Process Flow

Jump to bottom Edit New page

Pepe Bawagan edited this page Apr 21, 2014 · 5 revisions

1. A new request is created

Fields include description, location, and optionally amount and photographs.

2. OCD selects assessing agency

In parallel:

3a. OCD (validation)

Validation
- Sets isValid (i.e. did this really happen), which specifies whether or not this project should be done
Selection of tentative implementing agency
- Implementing agency simply sets permission for whatever agency is allowed to modify the request. That is, if at first the DPWH is set as the implementing agency and the DBM decides to change it to DILG, the implementing agency is set to DILG, and the DILG gets the permissions, while the DPWH permissions get revoked.

3b. Agency (domain-specific validation and assessment)

Validation
Uploads images and documents (includes program of works, BP 202, costing, reference diagrams and photographs)
Signoff

4. OCD reviews the existing document then signs off on it

5. OP marks proposal as approved for sending to DBM

6. DBM finalizes implementing agency

DBM can also choose to leave alone whatever the OCD has already set.

7. Assignment of SARO

Off-system: DBM generates SARO
DBM connects SARO to proposal in ticketing system, possibly by referencing OpenRecon request ID in eBudget
DBM "signs off" on the request, signaling that the SARO has been issued.
In the future, we may consider including a reference to the SARO in OpenRecon.