NGO Data and Knowledge Platform Requirements

contoh contoh model km n.w
1 / 16
Embed
Share

Explore the key requirements for a data platform in an NGO setting, including controlled vocabulary, granularity, aggregation, and knowledge capture. Understand how to accommodate experiences, know-hows, and innovations within the project dynamics.

  • NGO
  • Data Platform
  • Knowledge Platform
  • Requirements
  • Sustainability

Uploaded on | 0 Views


Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.

E N D

Presentation Transcript


  1. CONTOH-CONTOH MODEL KM Aliansi Masyarakat Adat Nusantara Pembekalan staff November 2023

  2. CONTOH 1: ORGANISASI PENGEMBANGAN KOMUNITAS (NGO)

  3. 1. NGO: 1. SYSTEM ORIENTATION - - The system should be easy to read and written by the users Yet it should be useful and able to carry it s function 1 Usability Project Management Ability to track project plan, execution,monitoring and evaluation 2 Decision sopport - - Ability to aggregate information across data dimensions Ability to pinpoint specific grain of Data 3 Knowledge Management - Ability to accommodate Experiences, and learning - Ability to pinpoint Know How, Know Why 4 - The project can be implemented from small, then expanded proportionally 5 Scalability Seamles Deployment - The project should be deployed, expanded and developed without stopping the current workflow 6

  4. Requirement as Data Platform 1. NGO: 1. REQUIREMENT AS DATA PLATFORM Controlled Vocabulary Pangkal pinang or Pangkalpinang or Pk. Pinang or Pangkal-pinang? Yogya or Yogyakarta or Jogja or Jogjakarta or D.I.Y.? Do we know the gender composition of beneficiaries? Do we know gender composition of the project staff? Which projects accomodates vulnerable groups? How many projects in single region during a certain span of time? How many common location are under many projects at once Granularity Machine readibility Can other subsistem extract data from it, and use it for other process (such as visualization, spatial analysis, data mining, etc) Aggregation Can one elaborate sum, averages, interpolations of data items ?

  5. 1. NGO: 3. REQUIREMENT AS KNOWLEDGE PLATFORM The platform should accommodate also the experience of workers on addressing their challenge Experiences Does the platform capture the know-how of doing things The platform should capture also the know why of the project dynamic Know How Know Why Solution, Improvement and innovation The platform should accommodate/capture the materials and dynamics of improvement on doing things, New way of doing things, and producing solution

  6. 1. NGO: 4. PRELIMINARY MODEL OF SITUATION Some people were involved in a project somehere with some specific goals and specific time The project goes through time, with achievements, difficulties and learnings, continued, monitored , evaluated, expanded List of themes, List of projects, List of workers, List of location Project proposals, Evaluation and monitoring, videos, photos, maps, financial reports, correspondences, publications Action Domain What happens daily Data Domain Document Domain Project is captured and viewed Managerial Domain Observation, analysis and decision

  7. 1. NGO: 5. COMPONENTS TO BE DESIGNED Wiki Pages design System Management W1 Wiki Text M1 Project authorities W2 Page Structure M2 Username controls W3 Hyperlink M3 Backup, Mirror and Migration W4 List Development manual M4 M5 Deployment manual M6 Interface to other systems Guidance and Rules File naming & storing conventions G1 Wiki Page and Edit Manual G2 Taxonomy of Objects G3

  8. 1. NGO: 6. IMPLEMEMTATION WORKS Wiki Platform Install W1 Media Wiki software installation W2 Media Wiki Customization Building the references Building basic databases G1 Building thesaurus G2 Taxonomy of Objects G3 Extracton Trasform and Load M1 Inspecting current repository M2 Scheduling and selectiong conversion M3 Backup, Mirror and Migration

  9. 1. NGO: 7. SUPPORTING SERVICES Content Assistance Training M1 Selecting some W1 Media Wiki software installation M2 Username controls W2 Media Wiki Customization M3 Backup, Mirror and Migration W3 Hyperlink Development manual M4 W4 List M5 Deployment manual M6 Interface to other systems Development assistance File naming & storing conventions G1 Wiki Page and Edit Manual G2 Taxonomy of Objects G3

  10. CONTOH 2: PUSAT PENELITIAN UNIVERSITAS

  11. CONTOH MODEL KM LEMBAGA PENELITIAN UNIVERSITAS Kapasitas sebagai lembaga penelitian Ketersediaan Hasil Masyarakat Seberapa jauh PPM mencapai cita- citanya Aras cita-cita organisasi Seberapa jauh aspek pengetahuan menyumbang pada cita-cita PPIM Strategi pengetahuan Ukuran Produksi Pengetahuan Aliran Simpan temu kembali Pemanfaatan Pengetahuan Aras aspek pengetahuan Pengetahuan Seberapa jauh operasional menyumbang pada aspek pengetahuan Aras operasional Jabaran kerja Pengembangan staf Jurnal Online Induksi Exit Pustaka diskusi Digital Fisik

  12. CONTOH 3: PERUSAHAAN SWASTA

  13. Manajemen Pengetahuan yang direncanakan (ekosistem pengetahuan) Aras Proses Bisnis Agile business High Turn Over Produksi Pengetahuan Aras Dinamika Pengetahuan Perolehan Pengetahuan Aliran pengetahuan Praktik Sarana P Aras S praktik lain Sarana dan praktik harian Sarana lain E2 E1 TRAINING LMS

  14. DELIVERABLE 2 : Prosedur-prosedur High Turn Over Agile business D2 Produksi Pengetahuan D21 DELIVERABLE 2 Prosedur-prosedur Prosedur-prosedur manajemen Aliran Perolehan Pengetahuan pengetahuan AV2 Sarana praktik D22 ADDED VALUE : Jabaran prosedur mengatur pralktek sehari-hari Prosedur prosedur keseharian dalam pengetahuan E2 E1 TRAINING LMS

  15. DELIVERABLE 3 : Alat ukur pengetahuan D31 High Turn Over Agile business Mengukur kontribusi pengetahuan D3 Produksi Pengetahuan D32 DELIVERABLE 1 INSTRUMEN PENGUKURAN PENGETAHUAN Mengukur berlangsungnya proses-proses pengetahuan Aliran Perolehan Pengetahuan pengetahuan Sarana Praktik AV3 Kerja-kerja dan dinamika pengetahuan dapat diukur, dan dapat selalu dipantau dan diarahkan D33 Mengukur berfungsinya sarana dan praktik keseharian E2 E1 TRAINING LMS

  16. DELIVERABLE 3 : Alat ukur pengetahuan D3 AV3 Kerja-kerja dan dinamika pengetahuan dapat diukur, dan dapat selalu dipantau Instrumen pengukuran pengetahuan dan diarahkan Berwujud KPI tambahan baru, maupun modifikasi dari KPI yang sudah ada - Memeriksa alat-alat ukur yang sudah ada - Modifikasi alat ukur yang sudah ada - Menambahkan alat ukur baru E3 Beberapa KPI relevan yang sudah ada di indosat

More Related Content