This heritage registry substantiates Frank’s 55-year career and more than 25 years online success.
Reading Time: 30 minutes
Practical Quality Plan has evolved through decades of hands-on deployment. From the MIL-I-45208 / MIL-Q-9858 eras to modern IA9100 standards, these technical records represent the objective evidence of Frank’s zero-defect history.
Technical standards have evolved – Zero-Defect integrity remains constant At-PQP™.
This heritage registry curates Frank’s legacy from the MIL-Q-9858 and MIL-I-45208 eras through to modern AS9100 and ISO 9001 deployments.
Whether it’s documenting a NASA Einstein Mission Traveler or establishing a Calibration System, these records are the forensic evidence of Frank’s 25+ year online success.
Here’s a legal snapshot:
- Colorado State ID: 19981084950 (established May 6, 1998)
- DUNS Number:
073949633 - CAGE Code: 5GXR2
Early Influence on a Career Path, 1970s
Frank was introduced to the Nassi-Shneiderman ‘if-then-else’ logic in 1974 where he started work as a Technician at Edcliff Instruments, Monrovia, CA in 1969. Frank applied the logic when he transformed to an RQA in the late 70s because all processes apply the same logic. He understands that ‘Follow-Through’ is a complex ecosystem of inputs and outputs.
If a Purchase Order is sent but the drawing revision is two steps from reality, or a recent Contract Mod changed the spec, or a Change Order is in-process, and the Supplier actually sent what was ordered, that’s several dinosaur eggs. The JnF catalog is built on this ‘What-If’ rigor – ensuring that every input leads to a verified, compliant output.
1974: The Nassi-Shneiderman Foundation
Long before the 36 findings from the NASA-SAC 2003 GAP survey, the “if-then-else” logic was forged here…
- The Paradigm Shift: Bridging the gap from prescriptive MIL-spec habits to structured AS9100 process logic.
- Progress Markers: Every finding in the 2003 NASA-SAC survey report was a step toward modernization.
Schedule Proof, 1981
Frank remembered a discussion, more like a plea from a department manager at EPI to sign a CofC before final acceptance. Don’t know if this was a test for a new hire, but Frank convinced the Dept Manager (Walt M.) that he could run the test in the high altitude simulation chamber at -65F for the Cupric Chloride/Magnesium radiosonde battery before delivery tomorrow.
The acceptance test was successful: Frank randomly selected the samples, activated the batteries, and performed the test according to the ATP, then signed the CofC. Guess Frank passed Walt’s test, since he stayed late to get’r done.
- ATP Mastery: Hands-on execution of Acceptance Test Procedures in high-altitude simulation.
- Infrastructure of Trust: JnF’s catalog is backed by the physical assets and legal records of a Top 10 NSF-ISR facility.
- The Commitment: Frank’s the ‘Workaholic’ who stayed late at -65°F to ensure the Cupric Chloride/Magnesium batteries were flight-worthy.
- The Heritage: This early-career discipline is what made closing 36 NASA-SAC findings possible; the rigor was already in the DNA.
- The Integrity: Frank’s been sitting at his desk since the EPI/EPT/MEPI/Hughes/Boeing, and Lockheed, Raytheon, GE, DOE, DLA, GD, Bell, and so many other Customers, maintaining the same ‘Until…’ concept that he has honed to this day.
- The Prerequisite: Validated testing results must exist before the pen touches the CofC – no signing based on good faith.
- The Result: The JnF catalog isn’t a ‘product’ Frank bought; it’s a Legacy he continuously improves.
- The Signature: Signing a CoC isn’t a clerical act; it’s the final “Yes” in a Nassi-Shneiderman decision block exercised by the ‘Until…’ Patriot.
- The ‘Until…’ Concept: Frank’s been staying late to get’r done since the early days…
On a Generational Note, 1980s
In the 1980s at EPI, Frank hired a young QC Tech named Greg F. Greg watched the RQA day-to-day, who coached him to attend some classes on the subject at the local Community College. Greg actually understood his contribution to the whole as a QC Tech, and was inspired, like Frank was at Edcliff Instruments, to seek a career as RQA. Today, Greg is a Director of Quality. Frank’s legacy isn’t just the hardware that powered the NASA Einstein Mission; it’s the modern leaders who learned that Quality isn’t a department – it’s a backbone.
In the early days at Edcliff Instruments, Frank observed the ‘Responsible Quality Authority’ was a dark, ‘Darth Vader’ persona – fierce and unyielding. While Frank embraced that early RQA’s effects, his nature tempered that persona into a Service of Help.
- The Persona: Frank’s Meyers-Briggs personality test revealed a WYSIWYG (What You See Is What You Get) leader. His ‘No’ wasn’t an act of power; it was a ‘Zero-Defect’ shield for the mission.
- The Team: Jenf used to joke that ‘Team’ meant “everyone doing what Frank says” – but the reality was a Symbiotic Stewardship. Management at EPI gave Frank ‘free-reign’ because they knew his ‘until…’ patriotism was never meant to harm, only to protect.
- The Heart: Frank cherished the responsibility of being a ‘key part of the whole.’ He didn’t just oversee the process; he assiduously guarded the welfare of the Company, Employees, Suppliers, Customers, and their joint efforts to achieve project goals.
Introduction to FAA PMA, 1980s
EPI was approached by a Customer for a part that needed a PMA. The FAA blessed the design drawings and the PMA quality program, but the Customer’s many paths to a solution found a just-in-time way to achieve their goal that caused the FAA to archive issue of EPI’s PMA certificate. The experience earned Frank a worthy OJT to apply another day.
Wait For It, 1990s
Eagle-Picher hired a lot of technical staff to keep up with demand in the 90s. Being the RQA meant more than just checking parts; it meant protecting the entire system – and everyone in it.
When a Technician was filled with grief over a crushed Super NiCd cell in a cell block they just assembled, Frank didn’t see “Operator Error”! Frank only saw the Request for Support noting the condition and circumstance of an observation. The “no-blame” culture in practice over 20 years before its mandate in IA9100. Every anomaly was recorded on a RFS to enable “lessons learned” and “improvement opportunities”. After the RCA and approval by the Responsible Authorities, the RFS reported the root cause as “Documentation” because it didn’t account for alternate torque wrenches (i.e., management).
The Technician was held harmless.
- The Catalyst: Training for assembly of a temporary cell block used a loud-click torque wrench.
- The Practice: Actual work activities applied a torque wrench without audible feedback.
- The Focus: “Just the facts, ma’am”.
- Documentation: The Request for Support is a ‘request’, not an accusation (no-blame).
- Management: Frank was grieving as well because the if-then-else logic for the torque wrench was missed in the training procedure.
- Opportunity: The root cause could be called “a crack in the system”; in fact, the improvement opportunity enabled a fresh exam of all training procedures.
- The Disposition: Documentation is the root cause (i.e., management did not account for alternates).
- Corrective Action: Reexamine all training procedures to reapply “if-then-else” logic.
- The Audit Resolution: This early mindset enabled “if-then-else” focus on the 36 findings from the 2003 NASA-SAC GAP survey, where 36 findings were not just buried, but systematically closed.
IA9100 Human Factors
- The No-Blame Mandate: Frank replaced the traditional “Nonconformance Report” in 2003 with the Request for Support (RFS) to foster a non-punitive reporting environment.
- Human Factors Integration: Every RFS requires an assessment of Human Factors (e.g., fatigue, distraction, or lack of resources) during root cause analysis to prevent recurrence, rather than assigning blame.
- Safety Heritage: This policy reflects a 20+ year commitment to “Human-Centered Quality,” ensuring that Employees are safe to report a condition, an observation, improvement opportunity, or way-to-go praise.
Heritage Registry: FrontPage Beginnings, 2001
Jennifer and Frank’s original website in 2001 began with FrontPage 2000 extensions on a CI Host webhost. Support for FrontPage extensions ended in 2003 to deprecate the old website, which resulted in a standard HTML web presence in 2003 – Jennifer and Frank’s meager beginnings…
PHYSICAL FOUNDATION: Original MS FrontPage 2000 Installation Media. The toolset used to architect Jennifer and Frank’s first digital QMS presence.
ASSET VERIFICATION: Case back showing original Product Key. Forensic proof of the licensed infrastructure used for the 2001 launch of thebestisbarelygoodenough.com
ORIGINAL FOUNDATION (2001) – thebestisbarelygoodenough.com. Established via MS FrontPage 2000.
ARCHIVE (2001): thebestisbarelygoodenough.com.
View Full 2001 Website PDF (Traceability Archive)
CATALOG TRANSITION (2003) – quality-control-plan.com. Launched Sept 11, 2003. Forensically verified via October 2003 RQA worklog.
ARCHIVE (2003): quality-control-plan.com.
View Full 2003 Website PDF (Traceability Archive)
Introduction to AISC 360, 2001
Eagle-Picher Technologies partnered with Hughes, El Segundo, to produce a Super NiCd™ for LESAT in 1989. As more and more spacecraft battery projects were added to the schedule, EPT decided to operate a waste-treatment facility in Nov 2000 with construction extending into late 2001.
During the construction, Frank visited with some of the Crew of Martinson Construction, LLC to learn about their quality program requirements. Turns out, the Company had a desire to get into AISC CSE. Over a few months, Frank worked with the Crew to develop a QMS for their Company, and that effort led Frank to develop a program for ISO 17020:1998 Bodies Performing Inspections and its 2012 update, which then led to AC291:2007 and its regular updates. Frank added comprehensive kits to keep up in the At-PQP™ shop.
Turns-out, every small, medium, and massive Company that has purchased a practical solution since 2001 has achieved their pedigree!
Over the years, JnF’s Customers have asked for help to tailor a quality program to fit their needs. Those calls for help produced quality programs for many industries, such as: API Spec Q1 Petroleum and Natural Gas, AAR M-1003 Railroad, AC 7004 Special Processes, ISO 13485 Medical Devices, NFPA 2112 Garments, FAA PMA, and FAA Repair Station QCM/RSM, and ODA, AS9003 Inspection and Test, Factory-Built Non-Residential Structures, Construction Management, and so much more…
All programs apply the ‘Until…’ concept with an eye on preventing dinosaur eggs (latent defects) that later hatch to eat your lunch.
Learn more about dinosaur eggs in Zapp! The Lightning of Empowerment: How to Improve Productivity, Quality, and Employee Satisfaction by William Byham and Jeff Cox.
Digital Signature, PGI Webmaster, August 7, 2001
Early in Frank’s career at EPI, he and a couple managers traveled to Sandia to visit with ‘Jim’ about their DOE battery project, and that’s when Jim introduced Frank to the in-progress Pyrotechnics Guild International convention. They had just enough time to stop at the convention on the way to the airport to allow Frank to see some of the “live” activities.
While busy at work sharing their catalog online, Jennifer and Frank proposed a volunteer position as Webmaster for the PGI, and was accepted as ‘JnF Specialties’. The previous volunteer, Mark Wray, provided Jennifer and Frank with original website files to continue the efforts. [View the tri-fold proposal handout]. Jennifer and Frank continued the PGI online presence for two years until the next PGI volunteer committed to the effort. The following ‘source code’ snippet from the 2001 PGI homepage represents a continuation of Frank’s ‘Until…’ concept.
Here’s the current PGI Homepage… and here’s that source code from Jennifer and Frank’s PGI page from 2001:
<HTML> <HEAD> <meta http-equiv=”Content-Type” content=”text/html; charset=windows-1252″> <META NAME=”Author” Content=”JnF-Specialties”> <TITLE>Pyrotechnics Guild International Inc.</TITLE> <script language=”javascript”> <!– hide javascript function showAlert () { alert (“Please allow up to one minute to download this webpage.”); } // done hiding –> </script> </HEAD>
Did you notice the above “please allow up to one minute to download”? Do you remember those 56KB modems that took forever to download a webpage?
The above is original source code from Aug 7, 2001 that suggests:
Before the cloud, there was the ‘Fire.’ The above 25-year-old snippet proves the longevity of Frank’s commitment to digital integrity.
NASA Audit Sequence, Detailed Evidence Suite (13-Page Verification Suite):
- GSFC Formal Assessment Authorization: Addressed to Frank Elias (Dear Mr. Elias).
- NASA Supplier Survey (5 Pages): Reports program names supported by earlier zero-defect deliveries.
- Then current NASA open purchase order S-69319-G for 38ea 9Ah S-NiCd™ cells, survey dated 7-23-03
- Facility In-Brief: Official start of the Sept 23-24, 2003 Assessment.
- NASA-SAC Assessment (Pages 1 & Final): Explicit mention of March 2003 internal audit record (40 findings) and Frank Elias’s signature on each Finding and Observation, accepting responsibility.
- Validation Artifact: Randall Boss (Lead Assessor) SAC Business Card.
- Facility Outbriefing: Terminal findings and NASA’s concluding evaluation.
- NSF-ISR Registration (AS9100:2004) The Aerospace Standard Certification
- NSF-ISR Registration (ISO 9001:2000) The Global Quality Standard Certification
RQA Summary: This forensic suite documents the transition from self-identified internal findings (40), to NASA-SAC assessment (36 findings), and terminal closure of ‘all findings’ via NSF-ISR issue of a Certificate of Registration for the EPT / MEPI QMS. [Open the 13-Page Verification Suite]
Metadata Traceability:
- September 23-24, 2003: NASA-SAC Facility Assessment
- GSFC Lead Assessor: Randy Boss (Supplier Assessment Center).
- Audit Team Specialists: Linda Sutton (Quality Systems), Larry Oien (Manufacturing), Chuck Allen (Manufacturing), and Bob Jaeger (Engineering).
- Objective: Agency-wide Supplier Assessment Initiative to evaluate critical processes and identify potential risks to NASA programs (Reference: GSFC Letter 9-8-2003).
- Outcome: Documented 36 improvement opportunities (findings) and five (5) observations for the EPT / MEPI QMS that eventually leads to the terminal closure of those 40 internal findings from March 2003 according to the Pre-Assessment audit performed by Murray G. of NSF-ISR.
- The RQA Anchor (Survey Page 5): Frank’s definitive “No” to Question #45 – a formal declaration of confidence in the zero-defect record for at least ten (10) previously delivered, zero-defect project milestones.
- The GSFC Mission Scope: Authorization for the CONTOUR-2 replacement bid and the 38-cell Super-NiCd™ flight order.
- Past Mission Validation: Proving the existing EPT QMS through Lunar Prospector, XTE/TRMM, Relativity, IMAGE, CONTOUR, SMEX, TOMS, FAST, NEAR, and TRIANA.
- The Proactive Trail: Documenting Frank’s “March 2003” internal audit (40 findings) preceded the NASA-SAC findings, proving the system was self-correcting.
- The Wet-Ink Authority: The formal GSFC letter signed by John M. Maristch (OSSMA).
The following out-of-sequence content is provided to “close the loop” for the above 2003 NASA Supplier Initiative.
NSF-ISR Report: Findings Closure – Terminal Resolution, Follow-Up to NASA Initiative
Context: Following the February 2003 Columbia (STS-107) disaster, NASA-SAC audits were initiated to eliminate “Normalization of Deviance” in safety protocols, as defined by the Columbia Accident Investigation Board (CAIB).
Documented Audit Resolution:
- Event: NSF-ISR Pre-Assessment Audit Report, May 2007.
- Evidence: 40 internal audit findings officially resolved and closed.
- Verification: [View NSF-ISR Pre-Assessment Report – See Page 5 for Closure Confirmation of internal audit findings]
- Logic Impact: NSF-ISR’s report independently verifies closure of 40 internal findings to mark EPT’s success for the transition from NASA’s old Supplier-control spec(s) to a new-modern QMS spec as defined by NASA’s supplier assessment initiative.
Heritage Registry: Frank’s Personal Log, October 2003
what-is-frank-doing-10-16-03.doc
IA9100 Context: Organizational Knowledge (Gained through Experience)
Forensic Application, October 16, 2003:
Frank’s extensive archive functions as a Centralized Knowledge Repository that preserves the “Paradigm Shifts” from the DCAS QAR Letter of Acceptance for MIL-I-45208 in the 80’s, to Lockheed’s acceptance of MIL-Q-9858 in the 90’s, and to AS9100 in the 20’s.
The contents of Frank’s personal log may have been the final-straw to create a paperless cyber solution to transition a complex QMS into an Efficient QMS™, which was actually created, released, and applied at EPT / MEPI in year 2004.
“The ‘Until…’ logic utilized in Frank’s modern eQMS was forged during the high-stakes battery manufacture for the NASA Gravity Probe B (GP-B) Mission, where single-point failure of any battery that powers a spacecraft is not an option.”
- Implicit Knowledge Capture: This Log validates the RQA’s role in resolving 36ea AS9100 NASA-SAC findings (expected progress markers/GAPs from MIL-Q to AS9100) ensuring that the “bones” of spacecraft battery reliability are embedded in every modern JnF procedure.
- Cross-Industry Traceability: Provides the 20-year “Digital Thread” connecting standards from Aviation-FAA, Medical Device, Construction, Oil and Gas, Railroad, Special Inspection, Aerospace, and more into a single, unified quality logic.
- Sustainability of Lessons Learned: Ensures that “Lessons Learned” from Kompsat-2 and earlier spacecraft projects are maintained as available organizational assets for decades later 2026 review.
Heritage Registry: AS9100 Paradigm Shift, 2003
what-is-frank-doing-10-16-03.doc)- Zero-Defect Rigor: Frank’s 2003 duties included managing Job #682 (NASA-SAC AS9100 GAP Survey) and performing receiving inspections for Job #630 deliverable supplies – proving the ‘Until…’ logic was active long before the first website sale.
- The First Kits: Frank documented the “production and release of quality management system documents,” including the first medical device and consumer credit counseling manuals, alongside the NASA Supplier initiative in 2003.
- Legacy Hardware: The “what-is-frank-doing” file confirms Frank’s RQA review, redline and approval of the KARI Kompsat-2 Mfg/QA travelers, providing a glimpse into a typical day related to “spacecraft projects” mentioned on the About Us page and below.
- Legacy Software: In the early 2000’s, there weren’t many cyber solutions for a QMS. This unyielding bar was the catalyst for Frank to envision a paperless, User-expandable cyber solution designed to apply continuous improvements as dynamic as the standard it supports. The birth of Efficient QMS™ was the answer to the paradigm shift, and a solution for the expense of 20 year data package storage, and for Frank’s self-preservation…
- Post-Columbia Era: Frank’s legacy was cemented in the high-stakes ‘post-Columbia’ era of 2003. When NASA mandated a top-to-bottom quality scrub, especially for the delayed and cost-overrun Gravity Probe B mission, Frank didn’t just survive the 36-finding SAC audit – improvement opportunities were used as a catalyst to bridge legacy MIL-spec into the modern AS9100 era.
- WYSISYG Note: During a voluntary Myers-Briggs personality assessment at Eagle-Picher in the 20’s, the test results revealed a striking contrast:
- 99% of people tested maintained a “presentation personality”.
- Frank tested as a pure WYSIWYG (What You See Is What You Get).
This lack of a ‘game face’ became Frank’s greatest forensic asset. - In the high-pressure aftermath of the Columbia disaster, NASA didn’t need a “presentation” – they needed to update their entire Supplier base to transform legacy standards to one quality system, especially for the over-budget and delayed Gravity Probe B mission that was under a microscope.
Cyber Pillar: ionCube Security, 2004
While Brian B. (eQMS Architect) was writing the framework to realize Frank’s vision, Jennifer and Frank identified “…digital integrity requires more than just a backup – it requires encryption.”.
- The Standard: Since 2004, Frank has applied ionCube encoded protection to secure the eQMS quality logic against unauthorized alteration.
- The Proof: As documented on ionCube.com March 2026 (see below screenshot), Jennifer and Frank’s ‘best effort’ to protect high-stakes operations is still active and ‘kicking’ at two eQMS demo locations 22 years later.
- The Result: Efficient QMS™ Users aren’t just getting a paperless quality system; they are deploying a secured, encrypted legacy that has protected operational programming for two decades.
Forensically verified screenshot from ionCube.com, March 2026:
2026: The IA9100 Evolution
The same Efficient QMS™ architecture that achieved AS9100 Top 10 Best Practice designation in 2007 is now positioned for conformity with IA9100 — the IAQG’s generational update to AS9100. Release 3.0 incorporates enhanced security architecture, CSRF protection, session hardening, and a user orientation system — the kind of “Digital Integrity” that IA9100 is only now mandating for the industry.
→ Experience the live working demo at onlinequalitysystem.com
eQMS is the digital skeleton — your policies, procedures, and forms are the muscle. Build them yourself, use free industry resources, or start with a professionally written QMS kit from the catalog.
Contact Frank to discuss free installation, free licensing, and no-charge tech support with no expiration when you install Efficient QMS™ on a public webhost.
Commercial Proof: Halliburton, 2005
Spanning a broad spectrum of Users from the Navy to the Energy Sector, the following is a fun fact in Frank’s heritage registry about a Halliburton purchase of an ISO 9001:2000 Service Quality Manual, but no receipt, only database info in backup files, 2005.
The following records for the Halliburton purchase on Jan 31, 2005 were reconstructed from legacy database archives. We figure the original HTML purchase receipt was lost during the 2006 migration from CI Host’s “end of FrontPage extension support” to a then-modern HTML webhost.
This transaction is confirmed through a synchronized Authorize.net transaction log and an AShop.sql backup file. This data provides a digital audit trail linking the originating IP address, Customer ID#, and delivered product.
- The Origin: FrontPage 2000 & thebestisbarelygoodenough.com (1998-2003) – transitioned to quality-control-plan.com when FrontPage extensions were deprecated.
- The Commercial Proof: Halliburton/KBR (2005).
- Years Later Defense Proof: Navy Oceanside/Bethesda (2011-2012).
- The Apex: Gravity Probe B / RQA (Responsible Quality Authority on station).
762700880CID #35 / IP 64.154.26.251ISO 9001:2000 Manual (Style 2)- Verified Origin: Transaction #762700880 was initiated on Jan 31, 2005, from IP 64.154.26.251, geolocated to the procurement region for KBR/Halliburton in Woodbridge, VA.
- Database Synchronicity: The AShop SQL dump (dated 4-30-2005) contains matching Customer ID (35) and Order ID (88) strings, proving the record existed in the live production environment prior to any server migrations.
- Historical Continuity: This deployment occurred during the
quality-control-plan.comcatalog era (est. Sept 2003), bridging the gap between Jennifer and Frank’s 1998 Colorado founding and the below 2011-2012 Navy purchases.
The above are really fun facts to share. Here’s another from the days of Resident QAR’s and Resident Boeing-Hughes PhD at EPT / MEPI:
FYI: Boeing acquired Hughes Electronics Space and Communications, October 2000
GD&T: Where Theory Meets Practice, 2005
Frank once visited with a Boeing-Hughes Resident PhD stationed at EPT / MEPI to request a change to a GD&T feature control frame on a Hughes drawing. Dr. Eddie S. considered the callout but didn’t think it could be changed. Frank hoped for a visit with their Engineer or Drafting guru, and Dr. Eddie S. agreed. EPT / MEPI didn’t have a CMM to determine conformity. Frank needed a callout that could be measured with a caliper on a jig, the old-fashioned way. Frank shared his callout with Drafting, who agreed, “that feature control frame” is less complex and doable on the bench with conventional M&TE to achieve the same results. Drafting convinced Engineering to revise the drawing. Dr. Eddie S. admired the simple-over-complex solution, and Frank was able to verify conformity using a “bench” set of M&TE.
- The Move: Visit with the Boeing-Hughes Draftsman.
- The Result: They agreed. Frank’s ‘simplified’ GD&T callout was easier to measure, faster to verify, and maintained the mission’s integrity.
- The Lesson: Quality isn’t a math problem; it’s a Verification Solution based on real-world application (don’t fix it… improve it…).
The Case of the “Smoking Gun”: A 55-Year Lesson in Integrity, 2007
Frank still chuckles (and snickers) at the memory of the only finding during the NSF-ISR certification audit. There he was, the RQA, personally escorting the Auditor to answer questions for the audit, when they stopped at a storage cabinet for shelf-life items. Checked its log, then checked its contents, then noticed an item set aside from all the rest. Turns out, the item was set aside because it was expired. Frank suspected a ‘responsible user’ with access had set the item aside to ‘deal with it later’, but it lacked the one thing that matters… a Withhold Tag, and the follow-through entrenched in the process – “withhold-tag and move suspect items” to the withhold area… another improvement opportunity manifests from a dinosaur egg…
- The Realization: Segregation without a Visual Trigger is just a delay of failure.
- The RQA Response: Frank didn’t ‘fix’ the item; Frank improved the protocol.
- The Value to You: Frank’s QCP templates are built from these ‘tender moments’ of reality. They don’t just follow the ISO/AS9100/IA9100 rules; they also account for the ‘loyal user’ with a ‘deal with it later’ mindset.
DoD Proof: US Navy, 2011
In a notable 2011-2012 sequence in Frank’s heritage path, online QMS resources were independently acquired by Navy Surface Warfare (Oceanside, CA) and Navy Warfare divisions (West Bethesda, MD) – a dual-coastal validation of real-world solutions – fun heritage registry fact, with records…
Transaction Receipts:
NAVY DEPLOYMENT (2011) – West Bethesda, MD.
NAVY DEPLOYMENT (2012) – Oceanside, CA.
Click/tap the above images to open a PDF of each complete receipt for show-and-tell, with original metadata for deep dive confirmation to confirm authorship.
Summary of Heritage Registry Timelines:
Before the global deployments and forensic database logs, JnF Specialties began with a single vision and the foundational tools of the early web.
Jennifer and Frank’s “meager beginnings” are preserved not just in memory, but in the physical media of the era:
- An original Microsoft FrontPage 2000 installation disk and a complete local backup of Jennifer and Frank’s 2001 digital presence, thebestisbarelygoodenough.com, captured on September 11, 2003.
- These artifacts represent the shift from traditional quality consulting to the digital delivery of compliance standards.
Following the September 2003 NASA-SAC GAP survey (Job #682) and its 36 findings, the QMS wasn’t patched, it was improved. The four-year paradigm-shift from 2003 to 2007 was dedicated to transitioning legacy MS Office-based policies into the high-reliability Efficient QMS™ HTML framework.
- June 2004 Foundation: Application of AS9100 Quality Policies Handbook and family of procedures into eQMS (Forensically verified via backup CD dated 7-18-04).
- EEI hired Consultant Christopher Paris from Oxebridge to finalize QMS docs 12-9-2005 to 12-19-2005
- The Result: Because the ‘Until…’ logic was already hardened through years of real-world LEO and GEO spacecraft projects (1989 LESAT, and 28 more, e.g.: KARI Kompsat-2, TRIMM, SMEX, IMAGE, ISS ELPS, etc, which produced thousands of hours of zero-defect cycling), MEPI achieved NSF-ISR Registration in just six months upon starting the formal Registration project on January 16, 2007.
- EEI hired Consultants Pietro (Pete) Savo and Dave Lombard January 31, 2007 to finalize plant preparations
Consultant Engagements and QMS Development (2005–2007)
December 2005 — ISO/AS9100 QMS Development
EEI engaged consultant Christopher Paris (Oxebridge) to finalize ISO/AS9100 Quality Management System documents. Two formal Design Reviews were held on December 9 and December 19, 2005. These meetings confirm adoption of QMS documents and established the action items that shaped the early structure of the system.
Source: Legacy eQMS SQL archive (file dated 9‑25‑2007).
Primary Source Extract — December 2005 (SQL)
January 31, 2007 — AS9100 Management Review and Plant Transformation
EEI hired consultants Pietro (Pete) Savo and Dave Lombard to finalize plant preparations for AS9100 certification. A full cross‑functional management review was conducted, marking the formal introduction of eQMS to all employees. Action items 1-26 were completed between January 5 and February 23, 2007, forming the operational foundation for EEI’s certification effort. Source: Legacy eQMS SQL archive (file dated 1‑1‑2009).
Primary Source Extract — January 31, 2007 (SQL)
AS RQA for EPT (acquired 10-03 by Mobile Energy Products Inc) the then MEPI’s 2007 AS9100 registration with NSF-ISR is forensic proof that Frank solved the ‘Digital Integrity’ puzzle 20+ years early:
- 2004-2007 Innovation: Frank moved quality management and data management from physical 3-ring binders and file cabinets to a structured, User-expandable, efficient digital environment (eQMS).
- 2026 Mandates: ISO 9001:2026 and IA9100 are only now engaging companies to treat digital data as a “controlled product.” Learn more about the true impact of IA9100 on the AQMS (110+ minute reading time).
- The Difference: Most companies in 2026 are reacting to these rules as a burden. Because of the Efficient QMS™ invention, Frank is simply validating a philosophy that he “lived-and-breathed” since the FrontPage 2000 era.
- In 2026, the global standards for IA9100 and ISO 9001 are finally mandating the ‘Digital Integrity’ and ‘Product Safety’ rigor that JnF Specialties has practiced for over 20 years.
- Efficient QMS™ (eQMS) wasn’t created to meet a 2026 requirement; it was born during the ‘can’t-fail’ goal of the NASA Supplier Assessment Initiative. As the Responsible Quality Authority (RQA) for complex products, Frank engineered a ‘Zero-Defects’ methodology that transitioned from the high-stakes laboratories of Eagle-Picher Technologies to the first “AS9100 Certified” digital/paperless eQMS for MEPI on July 10, 2007.
- Quote: “When you implement a JnF Specialties QMS, you aren’t just buying a program – you’re deploying a NASA-proven legacy. JnF’s systems are designed to be decades ahead, ensuring your QMS is as resilient as the hardware that powers a spacecraft.”
*Heritage Registry: Definition ‘Until…’ Concept
The RQA ‘Until…’ Concept: Total Product Accountability
At Eagle-Picher Technologies, the Responsible Quality Authority (RQA) maintained final disposition and release authority. This authority was never bypassed or diminished, even when a schedule was classified as expedited, high priority.
‘Until…’ is a promise of completion – a bridge to inform…
Why ‘Until…’ wins…
- The Continuity of Care: It encompasses the whole journey – from the first line of the contract until the final hardware is delivered with subsequent support. It suggests the RQA is the “Sentinel” watching over the product/process the entire time.
- The Curiosity Gap: The Curiosity Gap: Until it is right. Until it is safe. Until it can ship with total confidence – extending that duty to the Customer’s dock, ensuring safe handling and management in storage, precision in deployment, and responsible closure at end-of-life.
- EPT provides NASA with Handling and Storage Procedure for all complex products, especially for the GP-B batteries shipped in 2001 pending launch in 2004.
- ‘Until…’ is the voice of the RQA Patriot – the “How” to support the Company, Customer, and the end-use of the product.
- The Requirement: Final release of any product, process, or forensic record is withheld UNTIL objective evidence of zero-defect conformity is verified and documented.
- Expedited Protocol: High-priority corrections (any) are subject to the same ‘Until…’ rigor as initial production. No schedule or project milestone can supersede the RQA’s verification of effectivity/closure of nonconformities/corrective actions/calculated risks/engineering bulletins/CDDP, and more…
- Heritage Foundation: The concept is derived from the single-point failure risks of complex product manufacturing, where ‘Until…’ is the only acceptable timeline for mission critical hardware.
The RQA ‘Until…’ Concept: Full-Spectrum Accountability
“The Best is Barely Good Enough when failure is not an option.”
1. Operational Release Authority (IA9100 Cl. 8.1)
The RQA maintains the authority to Stop Work – on an expedited, high-priority basis – regardless of schedule pressure. Work remains halted UNTIL all safety/mission critical risks are mitigated and verified through objective evidence. There is no ‘priority’ higher than zero-defect conformity.
2. Corrective Action Accountability (IA9100 Cl. 10.2)
Corrective Actions (all) are subject to the same RQA rigor – on an expedited, high priority basis. A nonconformance is not closed, and a forensic record (any) is not finalized, UNTIL the RQA is satisfied that the ‘buried-bones’ of the nonconformity have been fully addressed, and the “live” thread is restored.
Gravity Probe B History and Mission Success
NASA Review of IA9100
The Foundation of Frank’s 55 Year Legacy
While this Registry documents the technical milestones of a Responsible Quality Authority, the true ‘Digital Thread’ is a 50-year, 6-month, and 13-day partnership with Frank’s ever so much better half, Jennifer (1945–2019). Jenf wasn’t just a spouse; she was the silent ‘RQA’ behind the scenes.
- The Commitment: From 21 year old Jennifer’s and 18 year old Frank’s 1969 start in a Las Vegas chapel, to the 2004 ionCube security deployment and so much more, Jenf supported the ‘Until…’ concept.
- The Availability: Jenf understood the ‘Fire’ that led Frank to answer the phone on weekends and vacations for Owners/Managers that needed an instant-pudding solution for a sudden Customer requirement.
- The Legacy: JnF Specialties exists because of a shared belief that integrity has no expiration date. This Heritage is as much Jenf’s as it is Frank’s.
Learn more about us
→ Experience the live Efficient QMS™ demo at onlinequalitysystem.com