Difference between revisions of "LKPP Project"

From PKC
Jump to navigation Jump to search
 
(2 intermediate revisions by the same user not shown)
Line 8: Line 8:
{{:LKPP/Requirements or deliverables}}
{{:LKPP/Requirements or deliverables}}
<HR>
<HR>
{{LKPP/Packages and complexity}}
{{:LKPP/Packages and complexity}}


===Team and skills===
===Team and skills===
{{LKPP/Team Type}}
{{:LKPP/Team Type}}
<HR>
<HR>
{{LKPP/team hierarchies,EntryLevel,effortTime}}
{{:LKPP/team hierarchies,EntryLevel,effortTime}}


===Budget===
===Budget===

Latest revision as of 02:25, 6 June 2022

Product proposal plan (description & budgeting)

Product description

To better serve Indonesia's goods procurement activities, the Coordinating Ministry for Maritime and Investments Affairs and LKPP spearheaded a pilot project to publish government approved product catalog data content online using Web3 technologies. The main feature of this Web3-base data service is to technically guarantee that data updating activities are transparent and non-corruptible. Knowing that both data content and relevant governing processes must evolve over time, therefore, in stead of just to a static software application that publishes electronic catalog data, it is necessary to create a meta Catalog(mCatalog), that can dynamically reflect the intricate dependency relations amongst evolving data content, changing policies written in natural languages, and evolving source code that involves many stakeholders of different levels of accountability. To integrate this many interacting parties, a new kind of knowledge management infrastructure, such as Project Knowledge Container(PKC), must be operated along side of this seemingly straight forward catalog data serving project. PKC as a data content and source code management platform, may serve as a single source of truth(SSOT), along with certain features in blockchain and Smart Contracts will be combined to guarantee data and policy transparency, as well as non-corruptibility of mCatalog as a Web3 data service product.

Product Scope

There is one infrastructure requirement:

PKC - Project Knowledge Container is a Web3 development framework and software toolbox that is embedded with a collection of web services and data management features to manage project requirement documentation, source code, and relevant data assets.

  1. Smart Contracts and Ethereum-based account classification to perform LKPP Feature
  2. Implement several web services like Matomo, Apollo Spreadsheets, Time metrics (CpL), IDE for programming education and so on
  3. Create proper documentation and guidance of the product to next levels of development and new team members
  4. Create documentation for discussion and improvement of the product, to align with the promotors and sponsors an understandable point of view and manage expectancies
  5. Create a better Interface, by controlling state-of-the-art UI/UX, including the awareness of web search optimization (SEO) and other means to promote a better experience with the user
  6. Improve the authentication process
  7. Implement the personal knowledge container as every user can have their own data center
  8. Integrate the features to allow areas such as learning, education, and professional industries to operate through the platform taking advantage of its features

Team and skills

  1. The owner is the actual chairman for PKC (Benjamin Koo, Professor)
  2. This project is directed through a project-oriented leadership which makes it to be run by a PMO and its project director, with strong IT background in SaaS and all the Web environments. The PMO will require several kinds of assistance according to the development of the product
  3. Programmers for Web Development for the core structure but also including UI/UX experts, DevOps and cybersecurity
  4. Designers and documentation experts for SaaS
  5. Other areas that will promote and manage the product into the market

  1. The Chairman, PMO and Core team is essential in the beginning of the project. It is predicted that 4 developers are esencital: 2 for Core development; 1 for authentication/BlockChain; 1 for Web interfaces (APIs and web design)
  2. After the first versions validated the level of security, interface design and web-services implementation will grow and the need for the team to double will be mandatory as well as the appliance of other roles such as DevOps
  3. The other roles on promotion, further assistance and product management into market will be required according to the steps of validation and predicted to be during October 2022
  4. To this project there are also high considered guest collaborators, invited by the Chairman, that should come and help on team building and promote also along the stakeholders and they will be required at the moment the versions are officially published

Budget

  • Implement the PMO structure, which involved in organizing documents, procurements, scheduling, budgeting and sub-projects and products. Assist on Chairman paperwork, revising text and helping it to be organized.
Cost: $10.000/month (PMO Director and assistant managers)
To Start in April 2022
  • PKC Core Development for construct and update
Cost: $3000/person/month) Requiring 2 developers TOTAL: $6.000/month
To Start in May 2022
  • Independent package: Web 3 Security Module
Cost: $3000/person/month) for 1 developer TOTAL: $3.000/month
To Start in June 2022
  • Design support UI/UX Design, Dev4X and Web4X expert, Integrative Testing, Data Analytics
Cost: $3000/person/month) Requiring 3 developers TOTAL: $9.000/month
To Start in June 2022
  • Aditional costs for Cybersecurity and Data Security Literacy, Cloud Service (AWS) Pay by Usage and PKC Turn-Key Hardware
Cost: $10.000/month
Apply in May 2022

Additionally, at all the WPs it is applied 25% of Overheads for management, administrative and unknown risks


  • TRL 1 - Phase 1 (End of June)
Packages = $74.000 *20% (overheads)
TOTAL = $88.800
  • TRL 2 - Phase 2 (End of September)
Packages = $114.000 *20% (overheads)
TOTAL = $136.800
  • TRL 1 - Phase 3 (End of December)
Packages = $114.000 *20% (overheads)
TOTAL = $136.800

Phases of delivery/Technology Readiness Levels(TRLs)

  • The current Proposal predicts to reach between TRL2 and 3
  • The realistic estimates predict that TRL3 can be published between end of October and December


TRL 1

previsional date to be validated: end of June

  • Run the first version Prototype and first environment controlled tests.
  • Consists in implementing Smart Contracts and Ethereum-based account classification to perform LKPP-defined product catalog data update and publication business process in PKC
  • Each business process would involve a set of explicitly defined roles, such as buyers/vendors/administrators, who are identified by Externally Owned Accounts
  • Ethereum-based account authentication and authorization services will be integrated with an application-specific account authentication data service as part of PKC, operated and administered by LKPP technical staff with technical support from this project team.
TRL 2

previsional date to be validated: end of September

  • Still in control environment but with a project to run independently in a real environment (predicted to be an education project)
  • Implement the security model of blockchain-based Smart Contracts achieving
  • Implement metric system based on time management and report real-time results
  • Report on a few low complexity use cases, identified by LKPP with the team implementation and data transparency and non-corruptibility


TRL 3

previsional date to be validated: December Can be certain updates between this period in order to make the product as much as updated to G20

  • Proof of Concept achieved by several tests in real and control environment and new features implemented
  • Authentication in process for private and public use. (Document the data types and data content categories in terms of what must be made public and what must be encrypted or stored privately. Define the data storage, backup/restore mechanisms leveraging the existing infrastructure of PKC)
  • Store and Contain, principle of a Personal Knowledge Container.(A specific data storage and backup/restore procedure, co-developed with LKPP will be the foundation for establishing guidelines for implementing the evolving business processes as they will necessary to be defined incrementally by LKPP when new requirements and needs reveal themselves)
  • Define strategies for the implementation in several means of education
  • Report on results with certain metrics such as the CpL

Note: At TRL3 the lessons learned will be fundamental to achieve the awareness and objectives of the product, which can and should be aligned between the promotors, the team and the market/users


To be further and better planned

Technology Demonstration and Deployment Process

To be reviewed

TRL 4

For 2023

  • Refine and ensure all code base can switch between public and self-hosted Ethereum-compatible blockchains, and works on generic web-based human-machine interfaces.
  • Demonstrate the PKC can serve as a framework to deploy and test varying versions of the same code base, include relevant web-based documentation that facilitate this overall project.

To be reviewed

TRL 5

2023 2nd Semester

  • Based on data types defined in TRL 3, present repetitive control structures in LKPP-defined business processes as standardized templates in Smart Contracts.
  • These standardized templates should be initially written in the programming language Solidity, and they are defined to enhance software reusability and reduce the complexity of business process verification and validation.

To be reviewed

TRL 6
  • Establish a full stack programming protocol (from secured data to user interfaces, or generically called Web3 programming protocol) for LKPP's blockchain catalog system. Starting from the beginning of the project, working with LKPP to define the look and feel of web interfaces, and incorporate UI/UX designers to create an adequate user experience that matches the expectation of stakeholders.
  • The UI/UX code base will incrementally converge with the Smart Contracts that are being developed in parallel, many design decisions will affect the code integration efforts and influence data service deployment processes.

To be reviewed

System/Subsystem Integration, Test and Product Launch

TRL 7
  • Develop working prototypes of modularized catalog data publishing and updating web services. * Work with an initial group of actual buyers/vendors/administrators as early adopters to validate the workflow.
  • Create automated or semi-automated test processes to load a significant amount of test data to stress test the system.

To be reviewed

TRL 8
  • Based on the Web3 programming protocol defined in TRL 6, this project phase will demonstrate that LKPP-defined business processes (relevant to catalog data publishing and editing), can be organized as modularized building blocks, as explicitly documented web pages with hyperlinked/version controlled data/source code assets, so that accountability of changes of data sources and data assets' control structures can be explicitly traced.

To be reviewed

TRL 9
  • Deploy LKPP's product catalog data service to the public. This deployment should demonstrate that web-based user interfaces, data backup/restore procedures, blockchain-based account and data transparency features, testing, usage statistics, user documentation, source code and data content version control can all be subsumed in an SSOT framework, namely Project Knowledge Container, as a meta catalog(mCatalog) of data and source code.
  • LKPP can utilize the above-mentioned features to evolve the overall functionalities of this product catalog service and potentially other web-based data intensive applications.