NatLabRockies / NatLabRockies/H2Integrate
Feature request: service business load
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 26
- Forks
- 44
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 16
Description
Service business load converter
Definition of a service business
A service business generates revenue by providing intangible expertise, labor, or specialized skills to clients rather than manufacturing or selling physical products. As discussed here, there is a continuous scale, not a hard line in determining a service business from other types.
Issue description
H2Integrate currently assumes all converters have a unitized product like steel, electrons, hydrogen, or heat. However, there are business cases of interest (e.g. data centers) that work on a service basis. I would like to be able to model the business case for such business with connected inflow streams. For example, I was working on this system for a data center and thought it would be nice to include the data center more completely.
Proposed solution
I think we could create a generic service business component with an output commodity of "services" or something similar that could be built upon for relevant system inputs for more specific service businesses.
Alternatives considered
Right now we just model down to the service business system to look at the inputs, which is generally sufficient from an energy perspective. However, I could see there being interest in modeling the service business loads as more than a demand for a commodity stream.
Additional context
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are identified. Start by reviewing the existing converter and connected inflow-stream component patterns to understand how unitized products are represented. Done means a generic service-business component can model service loads and relevant inputs without assuming a unitized output, with tests covering the new behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100