What can Build3 do for construction? Let's go over a few use-cases.
This section is dedicated to proposed use-cases with reference to a technical pallet implementation from the substrate framework.
Some are living in the source code, some are only conceptual. Each idea will vary in its development and is expected to grow in depth as contributors work through them.
Have more ideas? Join our to ask about joining the team!
You will see the note blocks as you read through the use cases. They each represent the level of development of the idea into the source code. They are defined as:
Stable Deployment.
Theory-based Idea. This means it can be implemented but hasn't made it into the production pipeline yet.
Abstract Idea: Requires high levels of customization or implementation method is unknown.
Alright, let's dive in...
A record of signed and verified work transactions.
The quality and throughput have never been reliably measured. It works for specific talents and personality types.
What we are talking about is a more true and revealing method of calculating what someone has contributed to their work. This allows for traditionally ignored traits of a worker can be made visible to the network.
The same protocols implemented in the engineering supervision use case also provide a more general-purpose proof of work for all players in the network. Any kind of work can be documented with this protocol.
There are three humans in this interaction.
Worker - The person that performs to the standard of care.
Reviewer - The person that reviews the work against the standard of care.
Authenticity Validator - The person that affirms both parties acted with good faith.
The review checks the work against the claimed standard of care. If approved on
Passes First Review: 10 tokens awarded to the worker
Second Review: 2 tokens awarded to the worker
Third Review: The total stake is lost and split between the network and burned
Reviewer is paid 1 token per review
The Authenticity Validator must affirm the authenticity of the transaction. If they reject the transaction, all parties lose rewards and stake.
The proposed frames to handle stamping engineered
The licensing boards will be constructed from the collective pallet.
We will also introduce a working group technical committee. Working groups define the standard of care for each category of work on the network.
The professional engineering license is modeled using the identity pallet. This pallet allows a user to put forth a proposed identity and ask for a review by any number of registrars.
An engineering board of directors may become a registrar on the network.
Adding registrars are currently done through the master admin (sudo); but will eventually be converted to a council decision.
The contracts pallet allows for the distribution of generic smart contracts which deploy into the blockchain and represent the professional interactions for each licensed activity on the network.
A user submits files (or links to files) to check their authenticity. The off-chain worker downloads the file, hashes and compares it to the state on contract, and emits and Event describes the findings.
on how to implement.
Creates an origin that requires multiple parties to sign before authorizing a transaction.
Kicking off a project may require a signature from the sales member as well as from the tehcnical director confirming all requirements are met for kicking the project off.
This pallet tracks the reported offenses.
A supervisory board regulating some issued credentials could submit disciplinary action against the Validator in accordance with their own regulations.
The community itself could check on the implemented standards of care and any violation would be reported as an Offense.
Allows account recovery if lost credentials based on M-of-N social recovery.
When a license is lost or stolen, this Pallet provides for a means of recovery which also secures the license.
A standard of care working group organized around the objective to establish a standard of care for a discipline type. In this case, Electrical.
It is the responsibility of the working group to establish a minimum standard of care for electrical design in a manner that
helps assure public safety
without imposing erroneous administrative work on the community that would discourage engagement in compliance
members of the working group should propose a standard_of_care and internally vote on the final version.
this final version would then go to the network as the proposed standard of care for the network
submissions will implement the staking mechanism (ie the group would collectively bond the proposal, receiving the bond back if adopted by the community
only one formal standard_of_care may exist per category.
A user may assign an identity to their prime account which would represent their main user information (name, email, etc).
When applying for a license, a user creates an account and adds it as a sub-account. The user then submits the sub-account to the board to make a judgment (approve) the identity. The board can change the state of the identity.
Once the license (sub identity) is approved, the engineer uses this license address to seal drawings.
Each professional enters into a Contract of Supervision when they begin working on a project.
This connects the licensed agents to the record of supervision for the project.
Because many jurisdictions require both the firm and the individual to be licensed, this contract may require authorization by both licensed parties: the firm and the individual.
Each individually permitted document should be deployed as a separate contract.
This Contract of Supervision should also store the state of the work contract including
deliverables - the list of deliverables and their state (percent completion).
discipline - the discipline associated with the supervision (elec, mech, etc)
standard_of_care - the standard of care implemented for the supervision
For the sake of practical implementation, we will limit the record of work to any substantial deliverable sent from professional outward which would increase the amount of completed effort by a minimum of 10 percent.
The Record of Work is a record of all major deliverable points, who performed the design, who checked the work, and who verified proof of the standard of care for the block entry.
For each record of work parties sign:
the designer submits work for review under a Minimum Standard of Care Configuration Trait
a reviewer checks work against theMinimum Standard of Care Configuration Trait
the professional signs that the document has been designed and backchecked per the Standard of Care
The contact may also be capable of recording payment history and terms. In the event of payment default, the contract would set the state of record drawings to invalid thereby prohibiting continued use of the construction documents (ie they would no longer be permitted for use in construction.
In the event of default, any queries to construction document status would
return an Error: Invalid Contract, Payment Default. NOT FOR CONSTRUCTION and
the contract would also engage the IPFS storage utility to encrypt the data to prevent further download until payment is remedied.
The contact may also be capable of recording payment history and terms. In the event of payment default, the contract would set the state of record drawings to invalid thereby prohibiting continued use of the construction documents (ie they would no longer be permitted for use in construction.
In the event of default, any queries to construction document status would
return an Error: Invalid Contract, Payment Default. NOT FOR CONSTRUCTION and
the contract would also engage the IPFS storage utility to encrypt the data to prevent further download until payment is remedied.
Validated a design without completing the checklist, this would be an Offence.The recovery process is protected by trusted "friends" and a specific threshold of that list is required to recover.
This helps to address the idea of an engineer losing "control" of their license.
the board could temporarily lock the license
any use of an illegal or invalidated license would notify the board
the engineer could go through the recovery process, and notify the board when recovered
when the account is recovered, the engineer can request it to be re-authorized (paying board fees as needed)
standard_of_care era is set to six months and is voted for adoption by network every six months. Any working group may submit an updated standard of care during that time if they have a better version. The network will vote on the standard of care.
A use case example for the PermitZIP Two-Week Project workflow.
PermitZIP offers a solution to the engineering world for a small project which is to provide a two-week turnaround. There are strict rules to follow for that to work on all fronts; one that often catches PermitZIP off guard is allowing a project to kick off before it should.
The biggest missing link is the sales team's knowledge of the required technical information to kick off into design. How do they know if the product data for the restaurant is to standard? How do they know if the architectural record documents have enough information for engineering judgment?
The same standard of care approach from the case is proposed. With the help of the sales team, a client follows the standard of care to prepare for kickoff.
This documentation, for example, includes:
Completed Survey
Cut sheets for special equipment
Architectural PDF (of the actual building)
Special equipment layout
They sign each transaction when they submit the required records. These records are reviewed by the sales team and authorized for final approval by the engineering production managers.
When all conditions are met, the two-week process begins and is documented on the blockchain smart contract.
DWG or Revit files
Signed proposal
Special project-related specifications (franchises, etc)