Intellectual Property & Data Rights
Rights are decided by who paid for the work and who can prove it. This page states how the institution establishes that record, asserts only what it can support, marks deliveries correctly, and respects the rights that belong to others.
Establishing the Baseline Before Award
Data rights disputes are almost always failures of record keeping that happened years earlier. The institution establishes what it owns, and how it can prove it, before a proposal makes any assertion.
- Inventory of pre-existing technical data and computer software developed exclusively at private expense
- Contemporaneous funding evidence for each item: what paid for it, when, and under which account
- Assertions listed in the proposal in the format the solicitation requires, with the basis and asserted rights category stated
- No assertion made where the funding record cannot support it
- Background material identified in teaming agreements so partners know what is and is not available
Rights Categories and What the Customer Receives
The government pays for rights and should get exactly what it paid for. Categories are applied by funding source rather than by preference, and delivered data carries the correct category on its face.
- Unlimited rights where development was funded by the government, and delivered as such without negotiation games
- Government purpose rights where development was mixed-funded, with the expiration understood and honored
- Limited rights in technical data and restricted rights in computer software where development was exclusively at private expense
- Specially negotiated license rights used where the standard categories do not fit the parties' intent, and documented in the contract
- Open-source and commercially licensed components identified with their license terms before delivery
Marking Discipline
An unmarked delivery can lose rights permanently; an over-marked delivery invites a challenge and damages credibility. Markings are applied at creation and verified again at submission.
- Legends applied in the exact form the contract clause prescribes, without invented or expanded language
- Marking applied at the file and drawing level at the time of creation, not retrofitted before delivery
- Pre-delivery review verifying that every deliverable carries a correct and supportable marking
- Nonconforming markings corrected promptly on notice rather than defended reflexively
- Challenge response prepared from the contemporaneous funding record, within the response period the clause allows
Protecting Others' Intellectual Property
The same rigor applied to the institution's own rights is applied to everyone else's. Customer data, teammate proprietary information, supplier designs, and third-party software are used strictly within the terms that convey them.
- Third-party software inventoried with license obligations tracked, including copyleft and attribution requirements
- Customer-furnished information used only for the authorizing contract and returned or destroyed as directed
- Teammate proprietary information handled under executed non-disclosure terms with access limited to those who need it
- Clean-room practice where independent development must be demonstrable
- Patent and infringement notification obligations under the contract honored on discovery
Invention Reporting and Technology Transfer
Federal contracts create invention obligations that are easy to miss and expensive to miss. Reporting is treated as a program deliverable with a schedule, not as an afterthought of the legal function.
- Employee invention disclosure required as a condition of employment, with a defined internal review
- Subject inventions reported to the agency within the period the patent rights clause requires
- Election to retain title and subsequent filing deadlines tracked as contract milestones
- Government license rights and march-in provisions understood and disclosed to leadership before commercialization decisions
- Technology transfer pathways, including SBIR data rights protection periods, managed against their expiration dates
Where This Connects
Data rights work connects to the legal division, capture and proposal discipline where assertions are made, export compliance for controlled technical data, and the research program, where independently funded development originates.
Alignment Disclosure
Monarch Space Systems describes its business integrity, property accountability, records, and data rights practices as aligned with the cited federal regulations, agency supplements, and consensus standards. Alignment is not a determination. The institution does not claim an approved property management system, an audited records program, a government determination on any conflict of interest matter, or any specific contract, customer relationship, or property holding. Case-specific facts, disclosures, and filings are handled with the responsible contracting officer rather than published.
Policy documentation, procedures, and control descriptions are available to customers and prospective teammates through the confidential engagement pathway or by request through institutional contact.