Open-Flame Readiness
Audit open-flame permit and safety readiness.
Description
Open-flame readiness involves production-specific controls and permissions.
Open-flame readiness involves production-specific controls and permissions. This audit compares declared control labels with confirmations while leaving evidence and approval review separate.1
Audit open-flame permit and safety readiness.
When to use Open-Flame Readiness
Use this tool to audit open-flame permit and safety readiness.
Prepare production measurements or checklist records for one planning period. Confirm units, staffing assumptions and caller-selected criteria before running the calculation.
How to use Open-Flame Readiness and understand its results
- Prepare production measurements or checklist records for one planning period. Confirm units, staffing assumptions and caller-selected criteria before running the calculation.
- Enter requiredControls, confirmedControls using the field table and calculation rules, then run the tool.
- Read coveragePercent, matched, missing, unexpected. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| requiredControls | Required open-flame controls | list of string | Required |
| confirmedControls | Confirmed controls | list of string | Required |
Enter requiredControls and confirmedControls label lists. Trim labels, reject blank entries and match case-insensitively with en-US lowercase. Deduplicate each list, requiring at least one distinct required item; an empty observed list is allowed. Return matched, missing, unexpected labels and coverage. Duplicate normalized labels keep their last trimmed spelling at the first key position.
coverage%=100 matchedDistinctRequirements/distinctRequirements Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| coveragePercent | Coverage (%) | number; minimum: 0; maximum: 100 |
| matched | Matched items | list of string |
| missing | Missing items | list of string |
| unexpected | Unexpected items | list of string |
{
"input": {
"requiredControls": [
"alpha",
"beta",
"gamma",
"delta"
],
"confirmedControls": [
"beta",
"alpha",
"extra"
]
},
"output": {
"coveragePercent": 50,
"matched": [
"alpha",
"beta"
],
"missing": [
"gamma",
"delta"
],
"unexpected": [
"extra"
]
}
}Limitations and assumptions
Coverage does not validate permits, fire precautions or permission to use an effect. Spelling differences beyond case and outer whitespace remain distinct.
Numeric inputs must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Lists are limited to 100,000 entries; the rules above may require smaller limits. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.
Alternative or Complementary methods
Use Rigging Sign-Off Audit: Audit required rigging sign-offs. For a complementary task, use Exit Capacity: Calculate exit capacity from supplied clear widths and capacity rate.
References
-
Open-Flame Readiness — tool.io
Similar or alternative tools
- Rigging Sign-Off Audit
Audit required rigging sign-offs.
- Exit Capacity
Calculate exit capacity from supplied clear widths and capacity rate.