8_Add_1_Exh_A_Functional-NonFunctional_Reqs_10.25.24.xlsx
XLSX spreadsheet 158 KB Posted
- Solicitation number
- 0000032868
- Issued by
- California
About this file
This document contains the functional and non-functional requirements for the California Department of Fish and Wildlife's (CDFW) Master Observation Database System (MODS) RFP #0078-02. The RFP seeks a contractor to implement a configurable or custom solution to develop and maintain a new MODS system that will provide the California Natural Diversity Database (CNDDB) program with the ability to capture, store, process, update and share observation point data, and increase efficiencies by incorporating data into the database as element occurrences in a timely manner. The contractor shall provide key services that include software development, infrastructure configuration, data migration, integration, training and maintenance & operations. MODS will replace the decades-old suite of databases and tools as a single database repository, consolidating several currently disparate database systems and processes. Proposals and eVAQ are due on 11/15/2024 at 10:00 AM PT.
The document outlines the detailed mandatory and desirable functional and non-functional requirements for the MODS system, including data management, validation, reporting, system integration, and user management capabilities. It also provides instructions for bidders on how to respond to the requirements. The system is expected to meet specific security, accessibility, and configurability standards to support the CNDDB program's needs.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 2_Attachment_13_Bidder_Qualifications_Workbook_09.23.24.xlsx | XLSX spreadsheet | |
| 6_eVAQ_Manual_for_Bidders.pdf | ||
| 3_Attachment_15_Key_Staff_Qualifications_Workbook_09.23.24.xlsx | XLSX spreadsheet | |
| 7_Addendum_1_RFP_0078-02_MODS_10.25.24.pdf | ||
| Q_A_Set_1_-_MODS_0078-02_RFP_10.25.2024.pdf | ||
| 1_RFP_0078-02_Master_Observation_Database_System_(MODS).pdf | ||
| 4_Exhibit_A_Functional-Non-Functional_Requirements_09.23.24.xlsx | XLSX spreadsheet | |
| 5_Exhibit_C_Cost_Worksheet_09.23.24.xlsx | XLSX spreadsheet |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
1. Instructions
| Tab 2 Functional Requirements (M) | |
| Description and Bidder Instructions | |
| 1 | Bidders shall fill out all rows beneath green-highlighted column F "Bidder Agrees." |
| 2 | Column A – Requirement # is the unique identifier of each individual requirement. Do not edit this column or its contents. |
| 3 | Column B – Level 1 Capability is the "L1 Capability" as it ties to the Business Capability Model (see Bidder's Library - Business Capability Model). Do not edit this column or its contents. |
| 4 | Column C – Level 2 Capability is the "L2 Capability" as it ties to the Business Capability Model (see Bidder's Library - Business Capability Model). Do not edit this column or its contents. |
| 5 | Column D – Priority is the category between Mandatory and Desirable Scored; all requirements are organized by Priority in tabs (all Mandatory requirements in “(M)” tabs and all Desirable Scored requirements in “(DS)” tabs. Do not edit this column or its contents. |
| 6 | Column E – Requirement is the detailed description of the requirement. Do not edit this column or its contents. |
| 7 | Column F – Bidder Agrees? is the dropdown for the Bidder to select “Yes” or “No” to indicate their response to the requirement. A “No” response to any Mandatory requirements may be grounds for dismissal of the Proposal. Bidders shall fill this column out for every row on Mandatory tabs. |
| 8 | No other columns or cells shall be edited or revised by the Bidder. |
| Tab 3 Functional Requirements (DS) | |
| Description and Bidder Instructions | |
| 1 | Bidders shall fill out all rows beneath green-highlighted columns F "Bidder Agrees" and G "Implementation Approach." |
| 2 | Column A – Requirement # is the unique identifier of each individual requirement. Do not edit this column or its contents. |
| 3 | Column B – Level 1 Capability is the "L1 Capability" as it ties to the Business Capability Model (see Bidder's Library - Business Capability Model). Do not edit this column or its contents. |
| 4 | Column C – Level 2 Capability is the "L2 Capability" as it ties to the Business Capability Model (see Bidder's Library - Business Capability Model). Do not edit this column or its contents. |
| 5 | Column D – Priority is the category between Mandatory and Desirable; all requirements are organized by Priority in tabs all Mandatory requirements in “(M)” tabs and all Desirable Scored requirements in “(DS)” tabs. Do not edit this column or its contents. |
| 6 | Column E – Requirement is the detailed description of the requirement. Do not edit this column or its contents. |
| 7 | Column F – Bidder Agrees? Is the dropdown for the Bidder to select “Yes” or “No” to indicate their response to the requirement. A "No" response to any Desirable Scored will omit any additional scoring the Bidder may be eligible for. |
| 8 | Column G – Implementation Approach is the dropdown for the Bidder to select how the requirement will be met, using one of the following three options below. Missed answers will omit any additional scoring the Bidder may be eligible for. |
| 9 | 1. “Standard" Functionality – the requirement will be met by the proposed solution’s standard functionality. |
| 10 | 2. “Integrated or Third Party” – the requirement will be met by an external component to the proposed solution. |
| 11 | 3. “Customizable” – the requirement will be met by custom development within the proposed solution. |
| 12 | No other columns or cells shall be edited or revised by the Bidder. |
| Tab 4 Non-Functional Requirements (M) | |
| Bidder Instructions | |
| 1 | Bidders must fill out all rows beneath green-highlighted columns F "Bidder Agrees." |
| 2 | Column A – Requirement # is the unique identifier of each individual requirement. Do not edit this column or its contents. |
| 3 | Column B – Capability is the technical/non-functional capability sub-grouping to which the requirement belongs. Do not edit this column or its contents. |
| 4 | Column C – Priority is the category between Mandatory and Desirable; all requirements are organized by Priority in tabs (all Mandatory requirements in “(M)” tabs and all Desirable Scored requirements in “(DS)” tabs. Do not edit this column or its contents. |
| 5 | Column D – Requirement is the detailed description of the requirement. Do not edit this column or its contents. |
| 6 | Column E – Bidder Agrees? is the dropdown for the Bidder to select “Yes” or “No” to indicate their response to the requirement. A “No” response to any Mandatory requirements may be grounds for dismissal of the Proposal. Bidders shall fill this column out for every row on Mandatory tabs. |
| 7 | No other columns or cells shall be edited or revised by the Bidder. |
| Tab 5 Non-Functional Requirements (DS) | |
| Bidder Instructions | |
| 1 | Bidders shall fill out all rows beneath green-highlighted columns F "Bidder Agrees" and G "Implementation Approach." |
| 2 | Column A – Requirement # is the unique identifier of each individual requirement. Do not edit this column or its contents. |
| 3 | Column B – Capability is the technical/non-functional capability sub-grouping to which the requirement belongs. Do not edit this column or its contents. |
| 4 | Column C – Priority is the category between Mandatory and Desirable; all requirements are organized by Priority in tabs (all Mandatory requirements in “(M)” tabs and all Desirable requirements in “(D)” tabs. Do not edit this column or its contents. |
| 5 | Column D – Requirement Text is the detailed description of the requirement. Do not edit this column or its contents. |
| 6 | Column E – Bidder Agrees? is the dropdown for the Bidder to select “Yes” or “No” to indicate their response to the requirement. |
| 7 | Column F – Implementation Approach is the dropdown for the Bidder to select how the requirement will be met, using one of the following three options below. Missed answers will omit any additional scoring the Bidder may be eligible for. |
| 8 | 1. “Standard" Functionality – the requirement will be met by the proposed solution’s standard functionality. |
| 9 | 2. “Integrated or Third Party” – the requirement will be met by an external component to the proposed solution. |
| 10 | 3. “Customizable” – the requirement will be met by custom development within the proposed solution. |
| 11 | No other columns or cells shall be edited or revised by the Bidder. |
RFP 0078-02 Master Observation Database System (MODS) Exhibit A: Functional and Non-Functional Requirements
California Department of Fish and Wildlife Contents:
This document contains the functional and non-functional requirements included with the CDFW MODS RFP as listed in the following order:
1. Tab 2: Response to Mandatory (M) Functional Requirements (EXHIBIT A: FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS)
2. Tab 3: Response to Desirable (DS) Functional Requirements (EXHIBIT A: FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS)
3. Tab 4: Response to Mandatory (M) Non-Functional Requirements (EXHIBIT A: FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS)
4. Tab 5: Response to Desirable (DS) Non-Functional Requirements (EXHIBIT A: FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS)
Bidders are required to provide answers to all Mandatory (M) requirements. A blank or "No" answer in this column will be deemed non-responsive and may be the basis for rejection of the Bidder's Proposal. Desirable Scored (DS) requirements are not mandatory but Bidders that met these requirements will earn points based on the implementation approach.
Additional information regarding Level 1 Capability ("L1 Capability") and Level 2 Capability ("L2 Capability") for Functional (M) and Functional (DS) Requirements can be found in the Business Capability Model (BCM) located in the Bidders Library.
For each requirement, Bidders are to indicate if they meet the requirement under the "Bidder Agrees" column by selecting "Yes" or "No" in the dropdown. For each DS requirement, Bidders must also indicate how the solution meets the requirement under the "Implementation Approach" column by selecting any of the following dropdown options:
Standard Functionality = Standard functionality or standard configuration (3 points) Integrated or Third Party = Standard API Integration or Third Party configuration (2 points) Customizable = Custom code change or custom developed feature (1 point)
These two (2) columns ("Bidder Agrees?" and " Implementation Approach") are highlighted in green for the Bidders for their response and entry. No other cells or columns should be edited by the Bidder.
2. Functional (M) Requirement # L1 Capability L2 Capability Priority Requirements Bidder Agrees?
(Y/N)
| F-M-DA-MO-001 | Data Acquisition | Manage Observations | Mandatory | The system shall maintain an audit log (historical record) for all source metadata records, source-element data, and individual observation records. |
| F-M-DA-MO-002 | Data Acquisition | Manage Observations | Mandatory | The system shall provide an audit logging feature to capture changes to observation and source records including the date of each change and the user responsible for the modification. |
| F-M-DA-MO-003 | Data Acquisition | Manage Observations | Mandatory | The system shall allow CNDDB staff to query the audit log. |
| F-M-DA-MO-004 | Data Acquisition | Manage Observations | Mandatory | The system shall allow for the display of the audit log (historical record) when the CNDDB staff access a source metadata record, and/or individual observation records. |
| F-M-DA-MO-005 | Data Acquisition | Manage Observations | Mandatory | The system shall grant role-based access to authorized CNDDB staff for rejecting observation records; they shall be catalogued but not used for creating Element Occurrences (EO). |
| F-M-DA-MO-006 | Data Acquisition | Manage Observations | Mandatory | The system shall provide role based access for authorized CNDDB staff to archive observation records. |
| F-M-DA-MO-007 | Data Acquisition | Manage Observations | Mandatory | The system shall provide role based access for authorized CNDDB staff to modify rejected flags on observation records. |
| F-M-DA-MO-008 | Data Acquisition | Manage Observations | Mandatory | The system shall provide role based access for authorized CNDDB staff to restore archived observation records. |
| F-M-DA-MO-009 | Data Acquisition | Manage Observations | Mandatory | The system shall provide flag features to indicate whether source-element data has been partially or fully mapped. |
| F-M-DA-MO-010 | Data Acquisition | Manage Observations | Mandatory | The system shall change the processing status of each observation record from unprocessed to mapped when it is added to an EO in the automated EO processing. |
| F-M-DA-POC-001 | Data Acquisition | Process Observation Changes | Mandatory | The system shall provide GUI tool(s) to display selected observation data records for CNDDB staff to review and update data. |
| F-M-DA-POC-002 | Data Acquisition | Process Observation Changes | Mandatory | The system shall allow authorized CNDDB staff to edit all observation data fields. |
| F-M-DA-POC-003 | Data Acquisition | Process Observation Changes | Mandatory | The system shall allow CNDDB staff to edit point, line, and polygon spatial data. |
| F-M-DA-POC-004 | Data Acquisition | Process Observation Changes | Mandatory | The system shall allow CNDDB staff to add internal notes/comments to all observation data records. |
| F-M-DA-POC-005 | Data Acquisition | Process Observation Changes | Mandatory | The system shall allow the CNDDB staff to update the processing status (Pending, Unprocessed, Rejected, and Mapped) of the individual observation records. |
| F-M-DA-POC-006 | Data Acquisition | Process Observation Changes | Mandatory | The system shall provide role based access for authorized CNDDB staff to make taxonomic updates to observation and source-element records when necessitated by a change in the element related tables. |
| F-M-DA-ROD-001 | Data Acquisition | Receive Observation Data | Mandatory | The system shall include functionality to replace the current Online Field Survey Form (OFSF) system for the submission of individual observations, including point, line, and/or polygon observation data. |
| F-M-DA-ROD-002 | Data Acquisition | Receive Observation Data | Mandatory | The system shall support ingestion of observation data captured through CNDDB's Survey 123 application. |
| F-M-DA-ROD-003 | Data Acquisition | Receive Observation Data | Mandatory | The system shall require users to log in to an authentication system to submit observation data in any data submission tool. |
| F-M-DA-ROD-004 | Data Acquisition | Receive Observation Data | Mandatory | The system shall verify contact information of data submitter via an authentication system for any data submission tool. |
| F-M-DA-ROD-005 | Data Acquisition | Receive Observation Data | Mandatory | The system shall validate the data submitted through any data submission tool as appropriate based on the following element categories: Plants, Spotted Owl, Bats, All Other Birds, All Other Animals. |
| F-M-DA-ROD-006 | Data Acquisition | Receive Observation Data | Mandatory | The system shall allow data submitters to modify any observation prior to the submission of the observations using the Bulk Upload Tool. |
| F-M-DA-ROD-007 | Data Acquisition | Receive Observation Data | Mandatory | The system shall enable the data submitter to continue and finish an incomplete data submission using any data submission tool. |
| F-M-DA-ROD-008 | Data Acquisition | Receive Observation Data | Mandatory | The system shall allow data submitters to access and download their submitted data files, to include details of any changes CNDDB staff have made to the records. |
| F-M-DA-ROD-009 | Data Acquisition | Receive Observation Data | Mandatory | The system shall maintain a copy of the data record(s) the user submits using any data submission tool. |
| F-M-DA-ROD-010 | Data Acquisition | Receive Observation Data | Mandatory | The system shall provide the flexibility for authorized CNDDB staff to edit the observation data field values and field validation rules within data submission tools. |
| F-M-DA-ROD-011 | Data Acquisition | Receive Observation Data | Mandatory | The system shall flag submitted observations that have yet to be reviewed by CNDDB staff as “Pending.” |
| F-M-DA-ROD-012 | Data Acquisition | Receive Observation Data | Mandatory | The system shall allow for the data submitter to upload tabular or geospatial observation data files of various types into a Bulk Upload Tool. |
| F-M-DA-ROD-013 | Data Acquisition | Receive Observation Data | Mandatory | The system shall provide the data submitter with a full review of the submission data uploaded via the Bulk Upload Tool before submitting the observation(s). |
| F-M-DA-ROD-014 | Data Acquisition | Receive Observation Data | Mandatory | The system shall allow association of attachments related to a set of observations (per data upload) submitted in any data submission tool. |
| F-M-DA-ROD-015 | Data Acquisition | Receive Observation Data | Mandatory | The system shall support point, line, and polygon spatial data inputs. |
| F-M-DA-ROD-016 | Data Acquisition | Receive Observation Data | Mandatory | The system shall allow for data submitters to generate a summary report of their submissions in any data submission tool. |
| F-M-DA-ROD-017 | Data Acquisition | Receive Observation Data | Mandatory | The system shall allow the data submitter to submit negative observation data in any data submission tool. |
| F-M-DA-ROD-018 | Data Acquisition | Receive Observation Data | Mandatory | The system shall enable data submitters to see their previously submitted observations in the database using any data submission tool. |
| F-M-DA-RO-001 | Data Acquisition | Report on Observations | Mandatory | The system shall allow CNDDB staff to query observation records by all observation record fields. |
| F-M-DA-RO-002 | Data Acquisition | Report on Observations | Mandatory | The system shall allow CNDDB staff to query source records by all source record fields. |
| F-M-DA-RO-003 | Data Acquisition | Report on Observations | Mandatory | The system shall allow for CNDDB staff to export queried observation data results as a shareable file type on their local machine. |
| F-M-DA-RO-004 | Data Acquisition | Report on Observations | Mandatory | The system shall generate automated frequency-based reports (weekly, monthly, and quarterly) from the source metadata records, source data, and/or observation records. |
| F-M-DA-RO-005 | Data Acquisition | Report on Observations | Mandatory | The system shall generate aging reports from the unprocessed source and observation data backlog using metrics from the source metadata table for number of unprocessed sources, number added in the last month, and number processed in the last month by plant and animal categories. |
| F-M-DA-RO-006 | Data Acquisition | Report on Observations | Mandatory | The system shall generate automated frequency-based reports (weekly, monthly, and quarterly) on observation collection volume (number of observations submitted). |
| F-M-DA-RO-007 | Data Acquisition | Report on Observations | Mandatory | The system shall use different symbology for positive and negative observations of a species at a location. |
| F-M-DA-RO-008 | Data Acquisition | Report on Observations | Mandatory | The system shall generate a report of the negative observation data. |
| F-M-DA-SO-001 | Data Acquisition | Source Observations | Mandatory | The system shall support the automatic creation of a source metadata record from the observation data submitted via any data submission tool. |
| F-M-DA-SO-002 | Data Acquisition | Source Observations | Mandatory | The system shall support the automatic creation of a source metadata record from the observation data captured through CNDDB's Survey123 application. |
| F-M-DA-SO-003 | Data Acquisition | Source Observations | Mandatory | The system shall determine and populate the source metadata record from any data submission tool with geographic information (quad and county spatial identifiers). |
| F-M-DA-SO-004 | Data Acquisition | Source Observations | Mandatory | The system shall determine and populate the source metadata record from the CNDDB's Survey123 application with geographic information (quad and county spatial identifiers). |
| F-M-DA-SO-005 | Data Acquisition | Source Observations | Mandatory | The system shall allow attached files to be associated with the individual observation records. |
| F-M-DA-SO-006 | Data Acquisition | Source Observations | Mandatory | The system shall assign unique identifiers to each source metadata record created. |
| F-M-DA-SO-007 | Data Acquisition | Source Observations | Mandatory | The system shall link each individual observation record to its associated source metadata record. |
| F-M-DA-SO-008 | Data Acquisition | Source Observations | Mandatory | The system shall assign unique identifiers to each observation data record created. |
| F-M-DA-SO-009 | Data Acquisition | Source Observations | Mandatory | The system shall be able to create source metadata records that do not have associated observation records. |
| F-M-DA-SO-010 | Data Acquisition | Source Observations | Mandatory | The system shall store the data submitters account information and contact information along with the submitted observations. |
| F-M-DA-SO-011 | Data Acquisition | Source Observations | Mandatory | The system shall allow one or more unique standardized identifiers (tags) to be assigned to individual observations (for example Spotted Owl master owl numbers). |
| F-M-DA-SO-012 | Data Acquisition | Source Observations | Mandatory | The system shall populate the source metadata record from any data submission tool with all required information/standardized fields provided. |
| F-M-DA-SO-013 | Data Acquisition | Source Observations | Mandatory | The system shall generate individual observation records from the data submitted using the Bulk Upload Tool. |
| F-M-DA-STO-001 | Data Acquisition | Store Observations | Mandatory | The system shall store all source metadata records, source data records, observation records, and submitted file attachments. |
| F-M-DA-STO-002 | Data Acquisition | Store Observations | Mandatory | The system shall store and provide access to point, line, and polygon observation data. |
| F-M-DA-STO-003 | Data Acquisition | Store Observations | Mandatory | The system shall be able to store provided data that conforms to the CDFW standard CNDDB observation template. |
| F-M-DA-STO-004 | Data Acquisition | Store Observations | Mandatory | The system shall allow for unique observation data fields for each element category. |
| F-M-DA-STO-005 | Data Acquisition | Store Observations | Mandatory | The system shall establish and create one-to-many relationships between the stored data/records. |
| F-M-DA-STO-006 | Data Acquisition | Store Observations | Mandatory | The system shall store and maintain a common set of field names for all observation records. |
| F-M-DA-STO-007 | Data Acquisition | Store Observations | Mandatory | The system shall allow for incoming source and observation data to be cross-walked and aggregated into standardized observation fields. |
| F-M-DA-STO-008 | Data Acquisition | Store Observations | Mandatory | The system shall provide role based access for authorized CNDDB staff to mark with a defined level of suppression (exclude from access) any selected source metadata record or observation record to allow for filtered outputs designated for different user groups. |
| F-M-DA-VD-001 | Data Acquisition | Validate Data | Mandatory | The system shall support data validation capabilities for the data submission tools to detect and flag potential abnormalities in data or spatial fields. |
| F-M-DA-VD-002 | Data Acquisition | Validate Data | Mandatory | The system shall detect potential data duplication/replication between pre-existing observations and new submissions. |
| F-M-DA-VD-003 | Data Acquisition | Validate Data | Mandatory | The system shall automatically flag and annotate a data record if any data duplication/replication is detected for any respective record. |
| F-M-DA-VD-004 | Data Acquisition | Validate Data | Mandatory | The system shall allow CNDDB staff to set element-specific expected spatial parameters (the borders of a given habitat for an element) using a species range and expected habitat maps. |
| F-M-DA-VD-005 | Data Acquisition | Validate Data | Mandatory | The system shall automatically flag incoming observation data that occurs outside of expected spatial parameters for the given element. |
| F-M-DA-VD-006 | Data Acquisition | Validate Data | Mandatory | The system shall automatically flag and annotate a data record if it detects any anomalous text and spatial data provided in standardized fields. |
| F-M-DA-VD-007 | Data Acquisition | Validate Data | Mandatory | The system shall allow the data submitter to override the alert to submit observations flagged as potentially duplicate and/or anomalous. |
| F-M-DA-VD-008 | Data Acquisition | Validate Data | Mandatory | The system shall alert the data submitter if any data duplication/replication is detected. |
| F-M-DA-VD-009 | Data Acquisition | Validate Data | Mandatory | The system shall alert the data submitter if any anomalous data is detected. |
| F-M-DA-VD-010 | Data Acquisition | Validate Data | Mandatory | The system shall utilize available range maps and models from element records to drive spatial data validation and determine whether an observation is outside the expected spatial area. |
| F-M-DE-CEO-001 | Data Enhancement | Create Element Occurrence (EO) | Mandatory | The system shall provide role based access for authorized CNDDB staff to customize standardized fields within the element occurrence forms. |
| F-M-DE-CEO-002 | Data Enhancement | Create Element Occurrence (EO) | Mandatory | The system shall allow for standardized fields within the element occurrence forms to be further customized as needed by CNDDB staff. |
| F-M-DE-CEO-003 | Data Enhancement | Create Element Occurrence (EO) | Mandatory | The system shall automatically create and store source features (spatial buffers that are precursors to EOs) for individual observation records. |
| F-M-DE-CEO-004 | Data Enhancement | Create Element Occurrence (EO) | Mandatory | The system shall retrieve and display all records of observations and source features based on element, geographic area, or other field criteria. |
| F-M-DE-CEO-005 | Data Enhancement | Create Element Occurrence (EO) | Mandatory | The system shall be able to determine whether source features from unprocessed observations can be aggregated into a new element occurrence or added to an existing element occurrence based on element-specific criteria. |
| F-M-DE-CEO-006 | Data Enhancement | Create Element Occurrence (EO) | Mandatory | The system shall enable an automated process that takes in all source features that are unprocessed for a given species or geographic area and generates or modifies an EO record accordingly. |
| F-M-DE-CEO-007 | Data Enhancement | Create Element Occurrence (EO) | Mandatory | The system shall allow automated EO processing to be scheduled, or be run on an ad-hoc basis. |
| F-M-DE-CEO-008 | Data Enhancement | Create Element Occurrence (EO) | Mandatory | The system shall allow automated EO processing to be limited to a specific element and/or geographic area. |
| F-M-DE-CEO-009 | Data Enhancement | Create Element Occurrence (EO) | Mandatory | The system shall populate the automatically created/updated element occurrence record with all respective information/standardized fields provided. |
| F-M-DE-CEO-010 | Data Enhancement | Create Element Occurrence (EO) | Mandatory | The system shall populate the automatically created/updated element occurrence record with the location reference data, such as lat/long, quad, county, elevation and PLSS values. |
| F-M-DE-CEO-011 | Data Enhancement | Create Element Occurrence (EO) | Mandatory | The system shall support the assignment of unique identifiers to individual element occurrence records |
| F-M-DE-CEO-012 | Data Enhancement | Create Element Occurrence (EO) | Mandatory | The system shall create a spatial feature record for an EO based on aggregated source features. |
| F-M-DE-CEO-013 | Data Enhancement | Create Element Occurrence (EO) | Mandatory | The system shall allow CNDDB staff to add source features where there is not an observation record. |
| F-M-DE-CEO-014 | Data Enhancement | Create Element Occurrence (EO) | Mandatory | The system shall allow CNDDB staff to edit source features for individual observation records |
| F-M-DE-CEO-015 | Data Enhancement | Create Element Occurrence (EO) | Mandatory | The system shall support the assignment of unique identifiers to spatial features. |
| F-M-DE-CEO-016 | Data Enhancement | Create Element Occurrence (EO) | Mandatory | The system shall provide an “Internal Notes” text field within the EO form for CNDDB staff to record notes. |
| F-M-DE-CEO-017 | Data Enhancement | Create Element Occurrence (EO) | Mandatory | The system shall associate and link supporting observation records, source-elements, and source features to element occurrence records for ease of reference and access. |
| F-M-DE-CEO-018 | Data Enhancement | Create Element Occurrence (EO) | Mandatory | The system shall differentiate between auto-generated, manually edited, and legacy element occurrences. |
| F-M-DE-CEO-019 | Data Enhancement | Create Element Occurrence (EO) | Mandatory | The system shall enable CNDDB staff to review auto-generated element occurrences to ensure data quality and accuracy. |
| F-M-DE-CEO-020 | Data Enhancement | Create Element Occurrence (EO) | Mandatory | The system shall allow authorized CNDDB staff to define and modify spatial and attribute rulesets for EO autocreation. |
| F-M-DE-CEO-021 | Data Enhancement | Create Element Occurrence (EO) | Mandatory | The system shall allow for the aggregation of some attributes from the related observation records into the EO record. |
| F-M-DE-ME-001 | Data Enhancement | Manage EOs | Mandatory | The system shall maintain an audit log (historical record) for all element occurrence records. |
| F-M-DE-ME-002 | Data Enhancement | Manage EOs | Mandatory | The system shall capture all attribute and spatial changes to EO record(s) in an audit log and detail the date of each change and who made the change. |
| F-M-DE-ME-003 | Data Enhancement | Manage EOs | Mandatory | The system shall display the audit log (historical record) regarding all changes/edits for each element occurrence selected by CNDDB staff. |
| F-M-DE-ME-004 | Data Enhancement | Manage EOs | Mandatory | The system shall allow CNDDB staff to query the audit log. |
| F-M-DE-ME-005 | Data Enhancement | Manage EOs | Mandatory | The system shall provide role based access for authorized CNDDB staff to archive EO records. |
| F-M-DE-ME-006 | Data Enhancement | Manage EOs | Mandatory | The system shall provide role based access for authorized CNDDB staff to restore archived EO records. |
| F-M-DE-ME-007 | Data Enhancement | Manage EOs | Mandatory | The system shall provide role based access for authorized CNDDB staff to delete archived EO records. |
| F-M-DE-PECU-001 | Data Enhancement | Process EO Changes & Updates | Mandatory | The system shall allow CNDDB staff to fill out or modify standard fields within the EO record. |
| F-M-DE-PECU-002 | Data Enhancement | Process EO Changes & Updates | Mandatory | The system shall allow authorized CNDDB staff to access, query, and edit all element occurrence data (spatial and attribute). |
| F-M-DE-PECU-003 | Data Enhancement | Process EO Changes & Updates | Mandatory | The system shall allow authorized CNDDB staff to create process status fields and configure the values for those fields. |
| F-M-DE-PECU-004 | Data Enhancement | Process EO Changes & Updates | Mandatory | The system shall allow authorized CNDDB staff to edit process status fields as needed. |
| F-M-DE-PECU-005 | Data Enhancement | Process EO Changes & Updates | Mandatory | The system shall allow authorized CNDDB staff to QC EO data. |
| F-M-DE-PECU-006 | Data Enhancement | Process EO Changes & Updates | Mandatory | The system shall allow authorized CNDDB staff to enter, edit, and/or remove any necessary notes in the QC process for needed corrections. |
| F-M-DE-PECU-007 | Data Enhancement | Process EO Changes & Updates | Mandatory | The system shall provide a “QC Return” flag for the EO record to be set if/when corrections to the EO are needed. |
| F-M-DE-PECU-008 | Data Enhancement | Process EO Changes & Updates | Mandatory | The system shall allow CNDDB staff to apply individual field and element changes within the element table that would be reflected in all associated EO records. |
| F-M-DE-PECU-009 | Data Enhancement | Process EO Changes & Updates | Mandatory | The system shall provide role based access for authorized CNDDB staff to make taxonomic updates to EO records when necessitated by a change in the element related tables. |
| F-M-DE-PECU-010 | Data Enhancement | Process EO Changes & Updates | Mandatory | The system shall notify assigned Mapper (CNDDB staff) if/when “QC Return” flag is set for an EO created by the Mapper. |
| F-M-DE-RE-001 | Data Enhancement | Report on EOs | Mandatory | The system shall allow CNDDB staff to query and search EO records by all EO standardized record fields. |
| F-M-DE-RE-002 | Data Enhancement | Report on EOs | Mandatory | The system shall allow for CNDDB staff to export queried element occurrence data results as a shareable file type on their local machine. |
| F-M-DE-RE-003 | Data Enhancement | Report on EOs | Mandatory | The system shall support the creation of formatted print-ready individual element occurrence reports. |
| F-M-DE-RE-004 | Data Enhancement | Report on EOs | Mandatory | The system shall generate automated frequency-based reports of the element occurrence records. |
| F-M-DE-RE-005 | Data Enhancement | Report on EOs | Mandatory | The system shall allow for generating reports that indicate the time elapsed since each element occurrence was last updated. |
| F-M-DE-RE-006 | Data Enhancement | Report on EOs | Mandatory | The system shall generate and provide the CNDDB staff with access to automated frequency-based reports on manual vs automatic EO update throughput. |
| F-M-DE-RE-007 | Data Enhancement | Report on EOs | Mandatory | The system shall generate and provide the CNDDB staff with access to automated frequency-based reports on Min/Max/Average time from submission of a new observation to verified completion of the element occurrence. |
| F-M-DE-RE-008 | Data Enhancement | Report on EOs | Mandatory | The system shall generate and provide the CNDDB staff access to automated-frequency-based reports on Max/Average time since the last Element Occurrence update by element. |
| F-M-DE-SE-001 | Data Enhancement | Store EOs | Mandatory | The system shall store and catalog all element occurrence data. |
| F-M-DE-SE-002 | Data Enhancement | Store EOs | Mandatory | The system shall store and provide access to spatial components of the element occurrence record(s). |
| F-M-DE-SE-003 | Data Enhancement | Store EOs | Mandatory | The system shall provide role based access for authorized CNDDB staff to mark with a defined level of suppression (exclude from access) any selected element occurrence record to allow for filtered outputs designated for different user groups. |
| F-M-DE-SE-004 | Data Enhancement | Store EOs | Mandatory | The system shall allow authorized CNDDB staff to update role-based permission settings for editing element occurrences. |
| F-M-DE-SE-005 | Data Enhancement | Store EOs | Mandatory | The system shall migrate all existing EOs in the current system into the new system. |
| F-M-DE-SE-006 | Data Enhancement | Store EOs | Mandatory | The system shall provide flagging and sorting capabilities to view element occurrences that were created from legacy and/or non-digitized observation data. |
| F-M-DE-SE-007 | Data Enhancement | Store EOs | Mandatory | The system shall flag EOs for review if/when supporting observation record(s) are updated. |
| F-M-DX-SDE-001 | Data Exporting | Schedule Data Exports | Mandatory | The system shall generate automated frequency-based reports on Threatened and Endangered Animal species list. |
| F-M-DX-SDE-002 | Data Exporting | Schedule Data Exports | Mandatory | The system shall generate automated frequency-based reports on Threatened, Endangered and Rare Plant species list. |
| F-M-DX-SDE-003 | Data Exporting | Schedule Data Exports | Mandatory | The system shall generate automated frequency-based reports on Special Animals list. |
| F-M-DX-SDE-004 | Data Exporting | Schedule Data Exports | Mandatory | The system shall generate automated frequency-based reports on Special Vascular Plants, Bryophytes, and Lichens lists. |
| F-M-DX-SDE-005 | Data Exporting | Schedule Data Exports | Mandatory | The system shall generate automated frequency-based reports on changes to the Special Plants list (Special Vascular Plants, Bryophytes, and Lichens). |
| F-M-DX-SDE-006 | Data Exporting | Schedule Data Exports | Mandatory | The system shall generate automated frequency-based reports on changes to the Special Animals list. |
| F-M-DX-SDE-007 | Data Exporting | Schedule Data Exports | Mandatory | The system shall allow CNDDB staff to download all automated frequency-based reports. |
| F-M-DX-SDE-008 | Data Exporting | Schedule Data Exports | Mandatory | The system shall provide role based access for authorized CNDDB staff to schedule the auto-export for public/subscriber-facing data artifacts and reports (for puposes of publishing manually). |
| F-M-DX-SDE-009 | Data Exporting | Schedule Data Exports | Mandatory | The system shall provide role based access for authorized CNDDB staff to manually trigger the auto-export for public/subscriber-facing data artifacts and reports. |
| F-M-DX-SDE-010 | Data Exporting | Schedule Data Exports | Mandatory | The system shall allow the CNDDB staff to edit/update the frequency of the automatically generated reports. |
| F-M-DX-SDE-011 | Data Exporting | Schedule Data Exports | Mandatory | The system shall allow for the generation of obscured location features for EOs flagged with a defined level of suppression upon data export. |
| F-M-DX-SDE-012 | Data Exporting | Schedule Data Exports | Mandatory | The system shall allow for the generation of obscured observations flagged with a defined level of suppression upon data export. |
| F-M-DX-SDE-013 | Data Exporting | Schedule Data Exports | Mandatory | The system shall provide role based access for authorized CNDDB staff to edit and configure the auto-export data packages and workflows. |
| F-M-DX-SDE-014 | Data Exporting | Schedule Data Exports | Mandatory | The system shall create a schedulable (monthly) snap-shot of the database for use as a static export. |
| F-M-EM-MER-001 | Element Management | Manage Element Ranking | Mandatory | The system shall allow CNDDB staff to flag an element whose rank needs to be updated. |
| F-M-EM-MER-002 | Element Management | Manage Element Ranking | Mandatory | The system shall allow authorized CNDDB staff to modify the rank computed by Biotics and record the reason for the change. |
| F-M-EM-MER-003 | Element Management | Manage Element Ranking | Mandatory | The system shall allow for the Biotics Element data (including ranks) to be ingested into the Element Table. |
| F-M-EM-MERT-001 | Element Management | Manage Element Related Tables | Mandatory | The system shall migrate all existing CNDDB taxa and element table data into the new system. |
| F-M-EM-MERT-002 | Element Management | Manage Element Related Tables | Mandatory | The system shall maintain element related tables that catalogue all elements and their required details. |
| F-M-EM-MERT-003 | Element Management | Manage Element Related Tables | Mandatory | The system shall provide an Element Group table that will provide a 1 to many relationship with the Element table, and can store Element Group-specific information, such as information for auto EO generation. |
| F-M-EM-MERT-004 | Element Management | Manage Element Related Tables | Mandatory | The system shall provide role based access for authorized CNDDB staff to set and edit required fields (columns) within the element related tables. |
| F-M-EM-MERT-005 | Element Management | Manage Element Related Tables | Mandatory | The system shall provide role based access for authorized CNDDB staff to add element(s) and all required details to the element table. |
| F-M-EM-MERT-006 | Element Management | Manage Element Related Tables | Mandatory | The system shall provide role based access for authorized CNDDB staff to edit and/or delete element related table records. |
| F-M-EM-MERT-007 | Element Management | Manage Element Related Tables | Mandatory | The system shall utilize the element related tables as the authority in receiving and recording observations (observations cannot be received for elements not listed on the element table). |
| F-M-EM-MERT-008 | Element Management | Manage Element Related Tables | Mandatory | The system shall allow authorized CNDDB staff the ability to group elements by use category for purposes of determining which elements we accept for submission of observations and the generation of EO data. |
| F-M-EM-MERT-009 | Element Management | Manage Element Related Tables | Mandatory | The system shall allow for synonomous element names to be included in the element table. |
| F-M-EM-MERT-010 | Element Management | Manage Element Related Tables | Mandatory | The system shall maintain a historical audit log of all element field updates. |
| F-M-EM-MERT-011 | Element Management | Manage Element Related Tables | Mandatory | The system shall provide an internal “Notes” text field for authorized CNDDB staff. |
| F-M-EM-MERT-012 | Element Management | Manage Element Related Tables | Mandatory | The system shall provide role based access for authorized CNDDB staff to mark with a defined level of suppression (exclude from access) any selected element record to allow for filtered outputs designated for different user groups. |
| F-M-EM-MERT-013 | Element Management | Manage Element Related Tables | Mandatory | The system shall maintain the defined level of suppression at the element level across all linked element data. |
| F-M-EM-MERT-014 | Element Management | Manage Element Related Tables | Mandatory | The system shall provide role based access for authorized CNDDB staff to attach internal element files to the respective element record. |
| F-M-EM-MERT-015 | Element Management | Manage Element Related Tables | Mandatory | The system shall associate spatial data sets to the respective element records to assist with observation validation. |
| F-M-EM-MTU-001 | Element Management | Manage Taxonomic Updates | Mandatory | The system shall allow authorized CNDDB staff to 'split' an element record (species taxonomic concept) into multiple element records. |
| F-M-EM-MTU-002 | Element Management | Manage Taxonomic Updates | Mandatory | The system shall allow authorized CNDDB staff to 'lump' element records (species taxonomic concepts) from multiple elements into a single element record. |
| F-M-EM-MTU-003 | Element Management | Manage Taxonomic Updates | Mandatory | The system shall maintain a historical audit log of all element table updates. |
| F-M-EM-MTU-004 | Element Management | Manage Taxonomic Updates | Mandatory | The system shall flag all observation, source-element, and element occurrence records that necessitate a review by CNDDB staff due to taxonomic update(s) on the element table. |
| F-M-EM-RE-001 | Element Management | Report on Elements | Mandatory | The system shall allow CNDDB staff to query the element related tables based on all standardized fields (columns). |
| F-M-EM-RE-002 | Element Management | Report on Elements | Mandatory | The system shall allow CNDDB staff to export query results into a shareable file that can saved to their local machine. |
| F-M-EM-RE-003 | Element Management | Report on Elements | Mandatory | The system shall allow CNDDB staff to export element record(s) within the element related tables into a shareable file that can be saved to their local machine. |
| F-M-EM-RE-004 | Element Management | Report on Elements | Mandatory | The system shall generate internal CNDDB historical log reports (element change reports) for user selected elements that detail all captured updates to the element and the element details, ranking updates, and species taxonomic updates. |
| F-M-EM-RE-005 | Element Management | Report on Elements | Mandatory | The system shall generate automated frequency-based reports on time since the last element ranking by element. |
| F-M-GO-MD-001 | General Operations | Manage Documents | Mandatory | The system shall provide a centralized document repository to store, search, and manage all documents. |
| F-M-GO-MD-002 | General Operations | Manage Documents | Mandatory | The system shall assign a unique identification number for each document uploaded . |
| F-M-GO-MD-003 | General Operations | Manage Documents | Mandatory | The system shall associate submitted documents with source metadata records, observation records, element occurrence records, and element records as appropriate. |
| F-M-GO-MD-004 | General Operations | Manage Documents | Mandatory | The system shall allow authorized CNDDB staff to configure the maximum upload size of submitted files. |
| F-M-GO-MD-005 | General Operations | Manage Documents | Mandatory | The system shall allow CNDDB staff to query and search source metadata records by all source metadata standardized record fields. |
| F-M-GO-MD-006 | General Operations | Manage Documents | Mandatory | The system shall support sorting of displayed records based on their attributes. |
| F-M-GO-MD-007 | General Operations | Manage Documents | Mandatory | The system shall support the filtering of displayed records based on their attributes. |
| F-M-GO-MGD-001 | General Operations | Manage GIS Data | Mandatory | The system shall use spatial data (GIS) to store location information for all records that require it. |
| F-M-GO-MGD-002 | General Operations | Manage GIS Data | Mandatory | The system shall provide spatial search and filtering functionality for all GIS data within an interactive map interface. |
| F-M-GO-MGD-003 | General Operations | Manage GIS Data | Mandatory | The system shall allow users to add, view, and query external map/feature services that meet Esri map service standards on the interactive mapping interfaces. |
| F-M-GO-MGD-004 | General Operations | Manage GIS Data | Mandatory | The system shall provide an interactive map-centric interface for all categories of data that include a spatial component. |
| F-M-GO-MGD-005 | General Operations | Manage GIS Data | Mandatory | All interactive map-centric interfaces shall include multi-dataset functionality, to include a table of contents containing a list of map layers included on the map, the option to add external map services, and the option to turn on/off each map layer independently. |
| F-M-GO-MGD-006 | General Operations | Manage GIS Data | Mandatory | The system shall allow authorized CNDDB staff to add, edit or delete the spatial data associated with any record (observation, source feature, or EO) in the system through an interactive map interface. |
| F-M-GO-MSI-001 | General Operations | Manage System Integrations | Mandatory | The system shall support batch processing. |
| F-M-GO-MSI-002 | General Operations | Manage System Integrations | Mandatory | The system shall provide a GUI to manage batch processes. |
| F-M-GO-MSI-003 | General Operations | Manage System Integrations | Mandatory | The system shall send alerts/notifications to the relevant CNDDB staff when an event occurs, indicating the status, completion, duration, start time, end time, success message, or failure error of the event. |
| F-M-GO-MSU-001 | General Operations | Manage System Users | Mandatory | The system shall provide role based access for authorized CNDDB staff to create user profiles and assign access levels for other CNDDB staff or other users. |
| F-M-GO-MSU-002 | General Operations | Manage System Users | Mandatory | The system shall provide role based access for authorized CNDDB staff to modify and/or remove user profiles. |
| F-M-GO-MSU-003 | General Operations | Manage System Users | Mandatory | The system shall allow authorized CNDDB staff to add or remove user roles with associated level of access. |
| F-M-GO-MSU-004 | General Operations | Manage System Users | Mandatory | The system shall provide a centralized user repository for authorized CNDDB staff to manage user roles and level of access. |
| F-M-GO-MSU-005 | General Operations | Manage System Users | Mandatory | The system shall authenticate both MODS internal users (CDFW staff) and external users (Data Submitters). |
| F-M-GO-MSU-006 | General Operations | Manage System Users | Mandatory | The system shall enable data submitters to register for an account. |
| F-M-GO-MSU-007 | General Operations | Manage System Users | Mandatory | The system shall send confirmation emails to verify user accounts and ensure their authenticity. |
| F-M-GO-MSU-008 | General Operations | Manage System Users | Mandatory | The system shall implement secure options for users to reset forgotten passwords, such as email-based password recovery or security questions. |
| F-M-GO-MSU-009 | General Operations | Manage System Users | Mandatory | The system shall enable authenticated users to access restricted documents and reports through an internet portal that requires authentication. |
| F-M-GO-MSU-010 | General Operations | Manage System Users | Mandatory | The system shall facilitate the submission of individual and/or multiple observations by data submitters. |
| F-M-GO-MSU-011 | General Operations | Manage System Users | Mandatory | The system shall allow for data submitters to be grouped by Organization such that data submitters within an Organization will be able to view submissions from others in the same Organization. |
| F-M-GO-MSU-012 | General Operations | Manage System Users | Mandatory | The system shall allow for primary users to manage the data submitter users within their Organization (such as to approve requests from data submitters to join their Organizational grouping). |
State of California
| Department of Fish and Wildlife | Exhibit A - Functional and Non-Functional Requirements |
| Tab 2. Functional Requirements (M) | RFP #0078-02 |
3. Functional (DS)
| Requirement # | L1 Capability | L2 Capability | Priority | Requirements | Bidder Agrees? | |
| (Y/N) | Implementation Approach |
(Standard = 3 pts;
Integrated or Third Party = 2 pts;
Customizable = 1 pt)
| F-D-DA-POC-001 | Data Acquisition | Process Observation Changes | Desirable | The system shall provide role based access for authorized CNDDB staff to establish workflow milestones for observation processing, review, quality control check, and completion. |
| F-D-DA-POC-002 | Data Acquisition | Process Observation Changes | Desirable | The system shall provide workflow flags for CNDDB staff to signal the clearance of established workflow milestones for observation processing; review, quality control check, and completion. |
| F-D-DA-POC-003 | Data Acquisition | Process Observation Changes | Desirable | The system shall provide role-based access for authorized CNDDB staff to apply edits to a set of selected observation records simultaneously (if the same edit for a particular field is required across multiple observation records, the system will allow application of that edit across all selected records). |
| F-D-DA-ROD-001 | Data Acquisition | Receive Observation Data | Desirable | The system shall allow for people listed as the observer in submitted data to have access to those records via the appropriate data submission tool. |
| F-D-DA-ROD-002 | Data Acquisition | Receive Observation Data | Desirable | The system shall enable the data submitter to modify their own data submission that has not yet been reviewed by CNDDB staff in any data submission tool by adding or changing files or information, along with a reason for the edits. |
| F-D-DA-ROD-003 | Data Acquisition | Receive Observation Data | Desirable | The system shall track and record any modifications made by the data submitter to their data submissions. |
| F-D-DA-RO-001 | Data Acquisition | Report on Observations | Desirable | The system shall allow for CNDDB staff to generate custom reports from the source metadata records, source data, and/or observation records using standardized metrics. |
| F-D-DA-RO-002 | Data Acquisition | Report on Observations | Desirable | The system shall allow CNDDB staff to add custom reports for observation records to the automated frequency-based reporting catalog. |
| F-D-DA-RO-003 | Data Acquisition | Report on Observations | Desirable | The system shall allow CNDDB staff to generate custom reports on observation collection volume. |
| F-M-DA-RO-004 | Data Acquisition | Report on Observations | Desirable | The system shall create spider diagrams from the Spotted Owl observations (those with the same masterowl number). |
| F-D-DA-VD-001 | Data Acquisition | Validate Data | Desirable | The system shall notify CNDDB staff if any duplicate data is submitted. |
| F-D-DA-VD-002 | Data Acquisition | Validate Data | Desirable | The system shall notify CNDDB staff if any anomalous data is submitted. |
| F-D-DE-RE-001 | Data Enhancement | Report on EOs | Desirable | The system shall allow for CNDDB staff to generate custom reports from the element occurrence records using standardized metrics. |
| F-D-DE-RE-002 | Data Enhancement | Report on EOs | Desirable | The system shall allow CNDDB staff to add custom reports for element occurrence records to the automated frequency-based reporting catalog. |
| F-D-DE-RE-003 | Data Enhancement | Report on EOs | Desirable | The system shall allow CNDDB staff to generate custom reports on manual vs automatic EO update throughput. |
| F-D-DE-RE-004 | Data Enhancement | Report on EOs | Desirable | The system shall allow CNDDB staff to generate custom reports on Min/Max/Average time from new observation to verified completion of the EO. |
| F-D-DE-RE-005 | Data Enhancement | Report on EOs | Desirable | The system shall allow CNDDB staff to generate custom reports on Max/Average time since the last Element Occurrence update by element. |
| F-D-DE-TW-001 | Data Enhancement | Triage Workload | Desirable | The system shall provide a work queue to triage element occurrence creation and/or revision either by element or spatial area. |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .