# BOSA & iO Digital 4: Government Procedure Builder ## Short Description **We want to develop an easy-to-use web tool for government administrators, with which they can design data-gathering flows for citizens (procedures).** For example, a flow for requesting a new identity card. They should be able to create, preview and publish these procedures, which can then be filled by citizens inside a new eGovernment app that is currently being built by BOSA & iO Digital: Digital Wallet. The web tool should make it easier for adminstrators to digitize paper processes, and should as a result increase the availability of digital procedures for citizens (via Digital Wallet), which are easier to fill than paper forms, for example, by reusing citizen data. ## Project **Project template:** **About the partners:** **BOSA:** The Federal Public Service (FPS, in NL/FR: “Beleid en Ondersteuning; Policy and Support”: BOSA) assists the government and supports the federal organisations in various areas: IT, HR, organisational control and integrity policy, budget, accounting and public procurement contracts. Especially relevant for this project is their aim to provide qualitative eGovernment support services. **iO:** iO Digital is working with BOSA to design and build an eGovernment app: Digital Wallet. *Your partners will give you a nice introduction as well on the first partner meeting!* ### Resources #### Research & context * Our partners will demonstrate Digital Wallet * Our partners at iO Digital will share summarized research insights that demonstrate the need for the tool #### Design * Design tool: Figma. * A Figma file of Digital Wallet designs will be provided. * Style components: the design component library of Digital Wallet will be provided. Keep in mind that the tool we'll build is meant for use by government administrators, and Digital Wallet is meant for use by citizens. Consider BOSA's style guidelines too. #### Code * Languages and frameworks are free to choose **Use case examples** * To get an idea of what kind of forms could be digitized by administrators, take a look at the [OSLO-Step's Domain Model example](https://purl.eu/cms/oslo-service/oslo-steps/domain_model.html). However, using that data model is not a necessity for this project. ### GitHub * **Team**: * **Repository**: ### **Discord Channel** \#procedure-builder ## File storage *For collaboration & storing files. Add the root folder to your drive:* [*https://drive.google.com/drive/folders/1rb3oaIVU9iHkVOaW\_oHK6w84JRqH0VR0?usp=sharing*](https://drive.google.com/drive/folders/1rb3oaIVU9iHkVOaW_oHK6w84JRqH0VR0?usp=sharing) {% embed url="" %} ## Team ### Coaches #### Lead [Thor Galle](https://thorgalle.me/) #### Support [Inti Valderas Caro](https://smoothsailing.be/team/inti-valderas-caro) ### Students Cyrille Mathieu - full-stack developer & student coach Joanna Kalisz - design Nicolay Camacho - front-end developer Aglim Benli - full-stack developer ### Specific councillors Sam Van Den Eynde (BOSA) iO Digital counselors: Maxime Van der Aa (week 1), Tim Wouters (week 2-4) ## Logo's ![Logo iO Digital SVG](/files/EWBZyhoBCBnxMrgcL5Rc) ![Logo BOSA SVG](/files/TUcT2fcyfsEriMI8dPID) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://help.osoc.be/osoc22/projects-partners/procedure-builder.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.