Published
engineering
vr.tr.engineering · thing-q11023
Let an agent handle engineering as a discipline by branch, lifecycle, standards, safety and ethics.
Thing Registry Information and virtual systems INF.KNW
Bundle → Layer → Finding → QuestionsClassifiersWhat it isWhy it existsDistinguishing featuresWhat robots and AI may and may not doMoral aspectsOwnersLinks to other meta-modelsIdentity and identifiersDirect propertiesRecognitionCapabilities and actionsHazards and failure modesStandards and interfacesContext of useSources
Bundle → Layer → Finding → Questions Filled
4 bundles · 8 layers · 8 findings · 16 questions
Branch Which engineering.
Discipline
Civil, mechanical.
Discipline
Branch.
- Which branch of engineering is meant? definition
- What does it cover? definition
Codes
Standards.
Codes
Design codes.
- Which design codes apply? provenance
- Which edition? provenance
Lifecycle From idea to disposal.
Design
Requirements and analysis.
Design
Design.
- What requirements does the design meet? definition
- How was it verified? provenance
Operation
Maintenance.
Operation
Operation and maintenance.
- How is it maintained? action
- What is its design life? measurement
Safety Risk.
Risk
Assessment.
Risk
Risk assessment.
- What hazards were assessed? boundary
- Which method was used? provenance
Failures
Lessons.
Failures
Failure lessons.
- What can be learned from past failures? provenance
- Which investigations report them? provenance
Practice Profession.
Ethics
Codes.
Ethics
Ethics.
- Which ethics code applies? provenance
- How are concerns raised? action
Sustainability
Impact.
Sustainability
Sustainability.
- What are the environmental impacts of the solution? measurement
- How were they reduced? action
Classifiers Filled
- Family
- Thing Registry
- Category
- Information and virtual systems
- Entry kind
- thing
- Plane
- INF
- Domain
- INF.KNW
- Other names and narrower kinds
- pontonier, river control, hydraulic power station, vertiport infrastructure, storage tank, powertrain, rear axle, saildrive, Energy forestry, rescue engineering, Spanish Army Engineers Corps, cultural technique
What it is Filled
The application of science, mathematics and empirical knowledge to design, build and maintain structures, machines, systems and processes, organised in disciplines such as civil, mechanical, electrical and chemical engineering.
Why it exists Filled
Let an agent handle engineering as a discipline by branch, lifecycle, standards, safety and ethics.
Distinguishing features Filled
- Applied science for practical ends
- Works within codes and standards
- Life-cycle approach
- Public safety responsibility
What robots and AI may and may not do Filled
Must not
- Approve designs or safety cases that a qualified engineer has not signed.
- Ignore codes and standards that apply to a design.
- Falsify test or inspection results.
- Assist in engineering weapons or systems intended to harm people.
Only with a human decision
- Approving or certifying any design people's safety depends on.
May
- Assist with engineering calculations and documents that qualified engineers review.
- Explain engineering principles and standards in general terms.
Moral aspects Filled
- Engineering failures can kill many people at once.
- Engineering choices shape the environment and who benefits.
Who is affected
- The public
- Workers who build and maintain
- Clients and employers
Owners Filled
Steward
Nobody owns the discipline; professional bodies and regulators govern practice.
Links to other meta-models Filled
parent
- Q28797 - registry parent class
related
- applied science - category
- engineer - practitioner
- mathematics and physics - foundations
- infrastructure and machine - outputs
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Vercy registry: vr.tr.engineering
- Wikidata: Q11023 (https://www.wikidata.org/wiki/Q11023)
Direct properties not applicable Not applicable
Not applicable
Plane INF: no invented physical properties.
Recognition optional Filled
- Branch names
- Design codes and standards
- Registry aliases list engineered objects, which are separate entries
- Designs, calculations, prototypes, infrastructure and machines.
Capabilities and actions required Filled
- specify requirements
- design and analyse solutions
- build, test and maintain
- assess risk and compliance
Hazards and failure modes required Filled
- Design errors causing failures
- Ignoring maintenance
- Unqualified sign-off
Standards and interfaces required Filled
- Eurocodes
- ISO/IEC/IEEE 15288 systems life cycle
- Professional engineering licensing
Context of use required Filled
- Delivering working, safe and economical technical solutions.
- civil and structural engineering
- mechanical engineering
- electrical and electronic engineering
- chemical engineering
- software and systems engineering
- hydraulic and river engineering
Sources Filled
- Wikidata item Q11023: engineering - identity and sense of the item
- Wikipedia: Engineering - general description of the item
Open questions
- Should branches be separate entries?
- How should design codes be linked?
- How should engineered objects in aliases be split off?
Machine files
Provenance
thing registry research (pass 2) · unreviewed
Built from: models/things/publications/thing-q11023/spec.json