-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DEQ TEMPO Integration #451
Comments
25.1.3
|
25.1.4
TEMPO has a table full of questions referenced by a Requirement ID. There are also tables representing different "templates" with their lists of Requirement IDs that apply to that template. Each question has a status and a comment (ie, the answer consists of two parts). 90% of their sites are Oil & Gas (O&G) and use the same template to determine the questions included in their inspections. This template may be updated over time. The other sites have a unique permit for each site. Each permit has its own unique list of Requirement IDs. A permit can also include a reference to a template to pull in those Requirement IDs as well. Each permit has a unique ID. A site's permit can be modified, which results in the creation of a new permit and it's ID. The desired output is a table indexed by both site and requirement ID containing the status and comment for each requirement ID for each site. The users must be able to use the survey in a place without cell coverage/internet. They also would like to be able to pre-populate answers with previous data. |
25.1.6Survey123 is not a viable option for the broad, expanded view Teri has. We will be meeting with her right before Q2 to figure out if she wants us to do a custom app. |
25.2.6Got an email from Teri on 18 Dec stating that they have staff internally working on TEMPO to S123 and will work with CGI for S123 to TEMPO. Sounds like we are no longer needed. |
Benefit
Assist DEQ in integrating TEMPO with Survey123 for their inspections.
Acceptance Criteria
Notes
Teri Houskeeper is the main contact
with CGI as the vendor.
Risks
Unclear direction, DEQ internal buy-in
Issue Reference
refs #
The text was updated successfully, but these errors were encountered: