S1000D / NAVAIR IETM Integration Specialist — U.S. Citizens Only
ABOUT WMAIR
WMAIR LLC is developing an evidence-preserving, multi-format technical-publication viewer and maintenance-information platform. The work supports our response to Navy SBIR , sponsored by the Naval Air Systems Command (NAVAIR).
We have a working company-funded prototype that currently demonstrates:
- Read-only technical-manual ingestion
- PDF text extraction and OCR
- Page-level evidence retrieval
- Exact source and page citations
- Manual-page image presentation
- Maintenance-manual, parts-catalog, wiring-diagram, and overhaul-manual search
- Role-based technician, QA, parts, and administrator workflows
- Source-file hashing and provenance
- A separate administrator-only S1000D Issue 6 validation laboratory
- API, retrieval, frontend, and regression testing
- Safety controls preventing invented procedures, invented part numbers, or return-to-service authorization
The existing prototype is research and demonstration software. It has not been approved by the Navy, does not currently claim Navy BREX compliance, and has not been integrated with a designated NAVAIR production environment.
We are looking for an experienced S1000D and NAVAIR technical-data specialist who can help us define a credible and technically correct integration path.
IMPORTANT: INITIAL ASSIGNMENT ONLY
The first contract is a limited, paid technical assessment.
The selected consultant will review our existing software, architecture, technical documentation, test evidence, and proposed Navy integration plan. The consultant will then provide recommendations describing what must be changed, added, validated, or documented before the software could be considered ready for integration with a NAVAIR technical-publication environment.
The initial assignment does not require the consultant to:
- Rewrite the software
- Perform full Navy integration
- Access a Navy network
- Access classified information
- Access Controlled Unclassified Information
- Convert operational Navy technical manuals
- Certify the software for Navy use
- Represent that Government acceptance has been achieved
- Commit to future work before a Phase II award
All initial-review materials will be public, historical, synthetic, or company-generated demonstration data.
INITIAL ASSESSMENT OBJECTIVES
The consultant will evaluate the prototype’s readiness to support an agnostic technical-publication viewer capable of handling the formats and data structures identified by the Navy.
The review should address:
1. S1000D architecture
- S1000D Issue 3.0, Issue 4.0, and later-issue considerations
- Data modules and Data Module Codes
- Publication modules
- BREX and project-specific business rules
- Applicability structures and cross-reference tables
- Common Source Database relationships
- Procedural, descriptive, fault, parts, and wiring information
- References between modules and external publications
- Version-specific schema, DTD, and mapping requirements
2. NAVAIR technical-publication environment
- Likely NAVAIR technical-data integration points
- NATEC/JEDMICS or other applicable NAVAIR ecosystems
- Designated IETM/IETMS viewer requirements when identified by the Government
- NAVAIR technical-data governance and acceptance processes
- Required interfaces, data packages, manifests, and validation evidence
- Areas that cannot be resolved until Government-furnished information becomes available
3. Multi-format viewer requirements
The Navy Q&A indicates that the desired solution is an agnostic viewer capable of reading or ingesting multiple technical-publication formats. The consultant should assess our proposed approach for:
- S1000D
- MIL-STD-3001 XML
- PDF and scanned PDF
- `.nci` files
- OEM or COTS technical-publication formats
- Other SGML, XML, raster, or legacy technical-data formats that may reasonably be encountered
4. Graphics and illustrated technical data
- Raster and vector graphics
- CGM files
- Information Control Numbers
- Hotspots
- Figure and sheet relationships
- Illustrated parts breakdowns
- Parts-list and figure relationships
- Wiring diagrams
- Missing-asset detection
- Graphic-reference validation
- Graphic adjudication and rendering
5. Data rights and markings
- Distribution statements
- Disposal markings
- Rights assertions
- DFARS markings
- Source-to-output marking preservation
- Object-level and package-level provenance
- Requirements that should be treated as mandatory acceptance gates
- Handling requirements for future ITAR/EAR-controlled or CUI technical data
6. Validation and acceptance
- XML, XSD, DTD, and BREX validation
- Reference validation
- Applicability validation
- Graphics and ICN validation
- Procedural-order validation
- Warning and caution preservation
- Defect classification and severity
- Error-detection and correction workflow
- Human adjudication
- Gold-standard datasets
- Recommended measures for accuracy, completeness, traceability, and residual error
- Evidence needed to distinguish technical feasibility from Navy acceptance
7. Search and information retrieval
- Search across heterogeneous technical-publication formats
- Task and system identification
- Applicability-aware retrieval
- Complete-task and complete-page coverage
- Typographical-error recovery
- Parts, figures, and wiring relationships
- Source citations
- Retrieval-confidence reporting
- Prevention of unsupported or invented maintenance information
- Human-review and authorization gates
8. COTS/GOTS and downstream integration
- Interface-neutral XML or JSON task packages
- Future integration with Government or commercial systems
- Ordered procedural steps
- Warnings, cautions, and notes
- Tools, materials, parts, and figures
- Applicability predicates
- Media and hotspot references
- Offline or disconnected operation
- Output suitable for later XR-headset or tablet presentation within an AR environment
- Clear separation between data presentation and maintenance authority
INITIAL DELIVERABLES
The initial contract should produce:
1. Prototype review
Review the existing application demonstration, architecture summary, relevant source-code organization, APIs, S1000D laboratory, data model, provenance controls, and test evidence.
2. Written integration-readiness assessment
Provide a concise written report identifying:
- Capabilities already demonstrated
- Technical deficiencies
- Unsupported assumptions
- Missing S1000D structures
- Missing NAVAIR requirements
- Viewer and interface gaps
- BREX and business-rule gaps
- Graphics and reference-handling gaps
- Data-rights and cybersecurity concerns
- Validation and testing gaps
- Items that must remain Government-furnished or TBD
3. Prioritized recommendations
Classify recommendations as:
- Critical before Phase I submission
- Recommended for the Phase I prototype
- Required during Phase II
- Dependent on Government-furnished information
- Dependent on a designated NAVAIR viewer or interface
- Future Phase III capability
4. Integration roadmap
Provide a practical roadmap showing how the current prototype could evolve toward:
- A Navy-aligned agnostic viewer
- S1000D and Navy BREX support
- MIL-STD-3001 XML support
- PDF, `.nci`, and COTS/OEM ingestion
- Graphics and ICN rendering
- NAVAIR technical-publication integration
- Automated validation
- Controlled search and retrieval
- COTS/GOTS output
- AR/XR-ready task-data output
5. Consultation meeting
Participate in one remote working session to explain findings, answer questions, and help WMAIR prioritize the next development activities.
INITIAL ASSESSMENT HOURS
Expected initial effort: approximately 4-9 hours.
A proposed allocation is:
- Software demonstration and kickoff: 1–2 hours
- Architecture and documentation review: 1-2 hours
- S1000D/NAVAIR gap analysis: 1-2 hours
- Written recommendations: 1–2 hours
- Final review meeting: approximately 1 hour
Applicants may recommend a different allocation, but this first contract must remain a focused assessment. It is not a complete system-integration engagement.
CONDITIONAL PHASE II OPPORTUNITY
If WMAIR receives a Navy Phase II award and the consultant’s initial work is successful, WMAIR intends to consider the consultant for a substantially larger follow-on role.
No Phase II work, minimum number of hours, or continued engagement is guaranteed. Any follow-on contract will depend on:
- WMAIR receiving the applicable Navy award
- The Navy’s negotiated Phase II statement of work
- Government-furnished technical data and business rules
- Export-control and security requirements
- Funding availability
- Consultant performance and availability
- SBIR subcontracting and workshare requirements
- Agreement on labor rates and contractual terms
ANTICIPATED PHASE II OBJECTIVE
The anticipated Phase II objective is to refine, scale, validate, and operationalize the agnostic viewer and related integration services developed during Phase I.
The system is expected to support more than one technical-publication platform or product library and to ingest representative Navy technical-publication data provided by the Government.
The consultant would serve as WMAIR’s S1000D/NAVAIR technical-data subject-matter expert. The consultant would guide the engineering team, review technical outputs, help establish acceptance criteria, and participate in Navy technical reviews.
ANTICIPATED PHASE II WORKSTREAMS
1. Government-furnished-information intake
- Review representative Navy S1000D technical publications
- Review the applicable Navy or project BREX
- Review project business rules
- Review applicability cross-reference and condition cross-reference structures
- Review distribution, disposal, rights, and DFARS markings
- Establish source inventories and controlled-data handling requirements
- Identify conflicts between public assumptions and actual Navy data
2. S1000D and standards baseline
- Establish the required S1000D issue and schema profiles
- Define version-specific handling
- Define BREX validation requirements
- Define project-specific business-rule handling
- Map technical-publication structures to the viewer’s internal data model
- Document S1000D, MIL-STD-3001 XML, PDF, `.nci`, and COTS/OEM profiles
- Define requirements for backwards compatibility and unresolved content
3. Agnostic viewer architecture and content semantics
- Review how the viewer represents documents, modules, tasks, steps, warnings, cautions, notes, tables, figures, parts, and references
- Define requirements for source-versus-rendered comparison
- Define provenance and revision-control behavior
- Review navigation and relationship handling
- Define handling of multi-volume publications
- Define configuration and effectivity behavior
- Support engineering decisions involving format adapters and canonical content objects
4. Applicability, configuration, markings, and rights
- Define applicability validation
- Review model, serial-number, configuration, and condition logic
- Define incompatible-content handling
- Define source-marking inheritance
- Establish fail-closed rules for unresolved restrictions
- Review object-level and package-level rights preservation
- Support legal and cybersecurity coordination when required
5. Graphics, ICNs, parts, and technical references
- Establish requirements for raster and vector graphics
- Define CGM and hotspot support
- Review ICN management
- Review illustrated parts and figure/list relationships
- Review wiring and schematic presentation
- Define missing-asset and broken-reference behavior
- Support graphics adjudication
- Verify that media remains connected to the governing technical content
6. Validation and correction system
- Define automated XSD, DTD, and BREX validation
- Define structural, semantic, applicability, reference, graphics, and marking checks
- Develop defect categories and severity levels
- Define fatal-error and warning thresholds
- Define correction and revalidation workflow
- Establish human-adjudication records
- Help create Government-reviewable validation evidence
- Support development of the accuracy and residual-error measurement framework
7. Search, retrieval, and task-data output
- Define technical requirements for task-level search
- Review query-to-source traceability
- Define complete-task and complete-evidence requirements
- Review configuration-aware retrieval
- Define unsupported-answer and insufficient-evidence behavior
- Review interface-neutral task packages for COTS/GOTS tools
- Define ordered steps, cautions, warnings, media references, and applicability output
- Support AR/XR-ready data contracts without treating AR presentation as maintenance authority
8. Navy viewer and system integration
- Participate in interface discovery with Navy stakeholders
- Review available Interface Control Documents
- Help map the WMAIR viewer to authorized NAVAIR technical-data environments
- Support NATEC/JEDMICS or other designated-system analysis when applicable
- Define import, export, authentication, logging, and audit requirements
- Review disconnected or restricted-network requirements
- Support integration testing
- Document unresolved Government dependencies
9. Technical validation and user evaluation
- Help establish representative test libraries
- Develop gold-standard evaluation cases
- Participate in technical-data-engineer adjudication
- Support review by certified instructors and qualified maintainers
- Review usability and technical-correctness findings
- Support error triage and corrective-action reviews
- Participate in test-readiness and demonstration events
10. Documentation, reviews, and transition planning
- Participate in technical interchange meetings
- Review architecture and validation deliverables
- Support monthly or milestone reviews
- Review Phase II reports
- Help prepare the Phase III transition baseline
- Document sustainment, rule-profile, schema, and content-governance requirements
- Support training and knowledge transfer
ANTICIPATED PHASE II SPECIALIST HOURS
Estimated total for this S1000D/NAVAIR specialist:
Expected average availability:
Approximately 15–25 hours per week, with higher effort during Government-data intake, architecture reviews, validation events, and final demonstrations.
These hours are a preliminary planning estimate, not a guaranteed commitment. The final hours will depend on the negotiated Navy statement of work, the number and complexity of product libraries, the Government-furnished formats, the applicable BREX and business rules, the designated integration environment, and the consultant’s final responsibilities.
ESTIMATED TOTAL PHASE II TEAM EFFORT
The specialist will not be expected to complete Phase II alone.
A complete Phase II effort would likely require a multidisciplinary team covering:
- Program and technical leadership
- S1000D/NAVAIR technical-data engineering
- Software and platform engineering
- XML and format-adapter development
- OCR, NLP, and search engineering
- UI and viewer development
- Cybersecurity and controlled-data handling
- Test automation and independent verification
- Aviation maintenance and technical-publication adjudication
- DevSecOps and deployment
- Quality assurance and documentation
Preliminary total WMAIR team estimate:
Approximately 18–24-month Phase II program.
This is a planning estimate only and will be revised after receiving the Navy’s negotiated requirements, Government-furnished data, applicable business rules, security boundary, and integration specifications.
MANDATORY U.S. CITIZENSHIP REQUIREMENT
This position is restricted to United States citizens.
Applicants must:
- Be a current U.S. citizen
- Reside in the United States
- Be legally authorized to work in the United States
- Be eligible to access ITAR/EAR-controlled technical information
- Be willing to provide reasonable documentation confirming U.S. citizenship before receiving controlled project material
- Disclose any circumstances that could limit access to export-controlled or Government technical information
Foreign nationals, non-U.S. citizens, and applicants requiring an export license for access to the anticipated technical information will not be considered for this engagement.
Do not submit citizenship documents through an unsecured Upwork message. WMAIR will provide an appropriate verification process if required.
REQUIRED PROFESSIONAL EXPERIENCE
Applicants should have substantial experience in several of the following areas:
- S1000D technical publications
- Navy or project BREX
- S1000D data modules and publication modules
- Common Source Databases
- Applicability and configuration management
- XML, XSD, DTD, XPath, and structured technical data
- IETM or IETMS viewers
- NAVAIR technical publications
- NATEC or JEDMICS environments
- MIL-STD-3001 XML
- MIL-DTL-81310
- Legacy PDF or SGML technical-manual conversion
- OEM or COTS technical-publication formats
- `.nci` technical data
- ICNs, CGM graphics, hotspots, and technical illustrations
- Illustrated parts catalogs
- Wiring diagrams
- Rights and distribution markings
- DFARS technical-data requirements
- ITAR/EAR and CUI technical-data handling
- Technical-data validation and acceptance
- Navy or Department of Defense software integration
- SBIR or STTR technical programs
PREFERRED BACKGROUND
The strongest applicants will have one or more of the following:
- Direct NAVAIR technical-data experience
- Prior work supporting Navy aircraft technical publications
- Experience developing or validating a Navy BREX
- Experience with S1000D Issue 3.0 and Issue 4.0
- Experience integrating an IETM viewer with a Navy environment
- Experience supporting NATEC, JEDMICS, NAWC-AD, or related NAVAIR organizations
- Experience defining acceptance criteria for technical-publication software
- Experience adjudicating procedures, figures, applicability, warnings, cautions, or parts data
- Experience translating technical-publication rules into software requirements
- Experience working directly with software engineers
- Experience participating in Navy technical interchange or program reviews
IMPORTANT SKILL EXPECTATION
This is not simply a software-development role.
The specialist must understand the operational meaning and technical-publication requirements behind the data. The consultant should be able to explain to software engineers:
- Which information is authoritative
- Which structures are mandatory
- Which relationships cannot be lost
- Which errors must block acceptance
- Which metadata may remain unresolved
- How applicability must be interpreted
- How graphics and parts references must be preserved
- How BREX and project business rules affect validation
- What evidence a Navy technical-data reviewer will expect
- Which claims WMAIR should not make before Government validation
CONFIDENTIALITY AND DATA-HANDLING EXPECTATIONS
The initial assessment will use public, historical, synthetic, and company-generated material.
The consultant must agree to:
- Protect WMAIR proprietary information
- Use project information only for the authorized engagement
- Avoid uploading project materials to unauthorized external systems
- Follow WMAIR access-control and data-retention instructions
- Preserve source-document restrictions and markings
- Report potential data exposure immediately
- Use only approved storage, communication, and collaboration methods
- Return or destroy project material when instructed
Future controlled-data work will be performed only within an authorized environment and under the applicable contract, security, export-control, and technical-data requirements.
ENGAGEMENT STRUCTURE
Initial engagement:
- Short-term
- Remote
- Fixed-price or hourly
- Approximately 6–12 hours
- Focused only on prototype assessment and recommendations
Conditional Phase II engagement:
- Only if WMAIR receives a Phase II award
- Potentially 18–24 months
- Primarily, remote. With possible traveling for presentatios for the Navy.
- Final schedule and compensation subject to award, negotiation, security requirements, and Government direction
HOW TO APPLY
Please provide:
1. A concise summary of your S1000D experience.
2. A description of your NAVAIR or Navy technical-publication experience.
3. The S1000D issues and BREX environments you have supported.
4. Examples of IETM, CSDB, XML, graphics, applicability, or validation work.
5. Your experience with NATEC, JEDMICS, NAWC-AD, or other NAVAIR organizations, if applicable.
6. Your availability for the initial 6–12-hour assessment.
7. Your hourly rate or proposed fixed price for the initial assessment.
8. Your anticipated availability for a conditional Phase II engagement.
9. Confirmation that you are a U.S. citizen residing in the United States.
10. Confirmation that you are eligible to work with ITAR/EAR-controlled technical information.
11. Any current or recent security clearance, if applicable. A clearance is not required for the initial public-data assessment.
12. One or two relevant professional references, if available.
PLEASE NOTE
This posting does not represent a Navy contract award or Government endorsement of WMAIR’s software.
The initial contract is solely for an independent technical assessment and recommendations.
Any Phase II opportunity is contingent on WMAIR receiving the applicable Navy award and successfully negotiating the follow-on scope.