{"component": "clause", "props": {"groups": [{"samples": [{"hash": "ak4KzxBBY5f", "uri": "/contracts/ak4KzxBBY5f#systems-engineering", "label": "Joint Research and Development Agreement", "score": 29.340862423, "published": true}, {"hash": "3GbfDCIqCvN", "uri": "/contracts/3GbfDCIqCvN#systems-engineering", "label": "Joint Research and Development Agreement (Second Sight Medical Products Inc)", "score": 23.8459958932, "published": true}], "snippet_links": [{"key": "design-controls", "type": "definition", "offset": [12, 27]}, {"key": "in-compliance-with", "type": "definition", "offset": [28, 46]}, {"key": "quality-management-system", "type": "clause", "offset": [57, 82]}, {"key": "the-fda", "type": "clause", "offset": [87, 94]}, {"key": "quality-system-regulations", "type": "definition", "offset": [97, 123]}, {"key": "system-components", "type": "clause", "offset": [239, 256]}, {"key": "risk-management-plan", "type": "clause", "offset": [353, 373]}, {"key": "test-plan", "type": "clause", "offset": [388, 397]}, {"key": "design-reviews", "type": "clause", "offset": [420, 434]}, {"key": "clinical-testing", "type": "clause", "offset": [496, 512]}], "size": 4, "snippet": "1.1. Update design controls in compliance with JHU/APL\u2019s Quality Management System and the FDA\u2019s Quality System regulations\n1.2. Conduct trade studies to evaluate currently-available commercial devices versus custom solutions for critical system components\n1.3. Maintain requirements database\n1.4. Maintain interface control documentation\n1.5. Maintain risk management plan\n1.6. Maintain test plan\n1.7. Conduct periodic design reviews (with Second Sight)\n1.8. Provide support to Second Sight for clinical testing preparation", "hash": "ab6f4b7beee009f23e8f97d0f5d8c1d1", "id": 1}, {"samples": [{"hash": "dMzudcDmNQC", "uri": "/contracts/dMzudcDmNQC#systems-engineering", "label": "Firm Fixed Price Contract (Xm Satellite Radio Holdings Inc)", "score": 18.0, "published": true}, {"hash": "aDDAFlTYwlA", "uri": "/contracts/aDDAFlTYwlA#systems-engineering", "label": "Firm Fixed Price Contract (Xm Satellite Radio Holdings Inc)", "score": 18.0, "published": true}], "snippet_links": [{"key": "work-package", "type": "definition", "offset": [0, 12]}, {"key": "milestone-completion-date", "type": "definition", "offset": [13, 38]}, {"key": "information-on", "type": "clause", "offset": [150, 164]}, {"key": "omitted-and-filed-separately-with-the-securities-and-exchange-commission", "type": "clause", "offset": [184, 256]}, {"key": "confidential-treatment", "type": "definition", "offset": [258, 280]}, {"key": "with-respect-to", "type": "clause", "offset": [300, 315]}], "size": 2, "snippet": "Work package Milestone Completion Date Payment -------------------------------------------------------------------------------- [*****] ***** Certain information on this page has been omitted and filed separately with the Securities and Exchange Commission. Confidential treatment has been requested with respect to the omitted portions.", "hash": "ff7cc8c6efc3076de302f25d9a5b6865", "id": 2}, {"samples": [{"hash": "2mWGd0T4ZWN", "uri": "/contracts/2mWGd0T4ZWN#systems-engineering", "label": "Contract", "score": 29.6227078775, "published": true}, {"hash": "ayqcKK7p7GW", "uri": "/contracts/ayqcKK7p7GW#systems-engineering", "label": "Contract", "score": 29.4420416172, "published": true}], "snippet_links": [], "size": 2, "snippet": "GCSS-MC/LCM Increment 1 is a fielded system in the O&S phase as defined in DoD Instruction 5000.", "hash": "e0d661e6e9c7cb039584cb24f7bb2a04", "id": 3}, {"samples": [{"hash": "34aH09cqGMe", "uri": "/contracts/34aH09cqGMe#systems-engineering", "label": "Contract", "score": 32.0261166128, "published": true}, {"hash": "ekSbc9rrfxq", "uri": "/contracts/ekSbc9rrfxq#systems-engineering", "label": "Contract", "score": 31.6675214598, "published": true}], "snippet_links": [{"key": "integrated-systems", "type": "clause", "offset": [4, 22]}], "size": 2, "snippet": "The Integrated Systems Engineering effort is CDRL-AAA.", "hash": "051c0e563124b96d436056052a241f51", "id": 4}, {"samples": [{"hash": "4teQdQisr38", "uri": "/contracts/4teQdQisr38#systems-engineering", "label": "Contract", "score": 31.8637510923, "published": true}], "snippet_links": [{"key": "the-contractor-shall-provide", "type": "clause", "offset": [0, 28]}, {"key": "performance-requirements", "type": "definition", "offset": [128, 152]}, {"key": "system-integration", "type": "clause", "offset": [208, 226]}, {"key": "system-reliability", "type": "clause", "offset": [267, 285]}], "size": 1, "snippet": "The Contractor shall provide systems engineering and systems engineering management to continually ensure that: \u2022 Applicable DO performance requirements are met \u2022 Applicable designs are feasible and sound\u200c \u2022 System integration and installation meet DO requirements \u2022 System reliability, availability and maintainability is evaluated \u2022 Delivered systems/equipment can be supported or sustained", "hash": "784fe42e8632cb7e26317e1332592670", "id": 5}, {"samples": [{"hash": "kU9QEkbBAWE", "uri": "/contracts/kU9QEkbBAWE#systems-engineering", "label": "Cih Transponder Contract (Ituran Location & Control Ltd.)", "score": 19.0, "published": true}], "snippet_links": [{"key": "functional-requirements", "type": "clause", "offset": [49, 72]}], "size": 1, "snippet": "4.3.1 SPECIFICATIONS Develop the CIH Transponder Functional Requirements as flowed-down from and with direct traceability to CIH Transponder spec (Ref 3,4,5).", "hash": "3bb78571d75196be20b6aaf46d886fde", "id": 6}, {"samples": [{"hash": "38BY5yuU1Vp", "uri": "/contracts/38BY5yuU1Vp#systems-engineering", "label": "Service Agreement", "score": 21.2806297057, "published": true}], "snippet_links": [{"key": "the-consultant-will", "type": "clause", "offset": [0, 19]}, {"key": "develop-project-management-plan", "type": "clause", "offset": [20, 51]}, {"key": "requirements-list", "type": "definition", "offset": [128, 145]}, {"key": "participate-in", "type": "definition", "offset": [174, 188]}, {"key": "the-final", "type": "clause", "offset": [243, 252]}, {"key": "concept-of-operations", "type": "definition", "offset": [253, 274]}, {"key": "the-preliminary", "type": "clause", "offset": [310, 325]}, {"key": "will-serve", "type": "definition", "offset": [479, 489]}, {"key": "basis-of", "type": "clause", "offset": [497, 505]}, {"key": "the-software", "type": "clause", "offset": [506, 518]}, {"key": "functional-requirements", "type": "clause", "offset": [519, 542]}, {"key": "the-concept", "type": "clause", "offset": [544, 555]}, {"key": "to-the-contractor", "type": "clause", "offset": [618, 635]}, {"key": "reference-document", "type": "clause", "offset": [662, 680]}], "size": 1, "snippet": "The CONSULTANT will develop Project Management Plan (PMP), Systems Engineering Management Plan (SEMP), and Contract Deliverable Requirements List (CDRL). The CONSULTANT will participate in two workshops with selected stakeholders during which the final Concept of Operations for the ATM will be developed from the Preliminary Draft Concept of Operations developed previously under the existing \u2587\u2587\u2587\u2587\u2587\u2587-\u2587\u2587\u2587\u2587 and Associates, Inc. Agreement P320-13-016. These Concepts of Operations will serve as the basis of the software functional requirements. The Concept of Operations developed as part of this work will be provided to the Contractor for the NEON Project as a reference document.", "hash": "f14c146171ec22796964108242208c81", "id": 7}, {"samples": [{"hash": "6BEgliv5NrF", "uri": "/contracts/6BEgliv5NrF#systems-engineering", "label": "Contract", "score": 32.6995090375, "published": true}], "snippet_links": [{"key": "engineering-plan", "type": "definition", "offset": [15, 31]}, {"key": "technical-approaches", "type": "definition", "offset": [101, 121]}, {"key": "space-vehicle", "type": "definition", "offset": [156, 169]}, {"key": "system-components", "type": "clause", "offset": [178, 195]}, {"key": "system-requirements", "type": "clause", "offset": [222, 241]}, {"key": "management-and-review", "type": "clause", "offset": [283, 304]}, {"key": "under-this-contract", "type": "clause", "offset": [492, 511]}, {"key": "to-maintain", "type": "clause", "offset": [603, 614]}, {"key": "established-requirements", "type": "definition", "offset": [619, 643]}, {"key": "requirements-traceability-matrix", "type": "definition", "offset": [670, 702]}, {"key": "the-contractor-shall-provide", "type": "clause", "offset": [704, 732]}, {"key": "the-system", "type": "definition", "offset": [760, 770]}, {"key": "allocated-to", "type": "definition", "offset": [822, 834]}, {"key": "system-support", "type": "clause", "offset": [874, 888]}, {"key": "by-the-contractor", "type": "clause", "offset": [1010, 1027]}, {"key": "configuration-management-system", "type": "clause", "offset": [1073, 1104]}, {"key": "management-process", "type": "clause", "offset": [1151, 1169]}, {"key": "contractor-assessment", "type": "definition", "offset": [1188, 1209]}], "size": 1, "snippet": "C.3.9.1 System Engineering Plan (SEP) - The Contractor shall develop and/or maintain SEPs to include technical approaches, changes and modifications to the Space Vehicle, Ground System Components, and UE specifications of system requirements (CDRL A00A).\nC.3.9.2 System Requirements Management and Review - The Contractor shall develop and/or maintain System Requirements Specifications (SRSs) \u2013 Physical, Functional, Performance) Baseline for architectures, services, and products developed under this Contract (CDRL A00B). The Contractor shall also conduct periodic System Requirements Reviews (SRRs) to maintain the established requirements baseline and maintain the Requirements Traceability Matrix. The Contractor shall provide traceability mappings from the system requirements baseline for each of the requirements allocated to the handset, space vehicle, and ground system support components. After the system requirements baseline and system traceability mapping is established, it will be controlled by the Contractor with changes managed through and appropriate Configuration Management system. Risks identified as part of the requirements management process shall include the Contractor assessment of ranking and mitigation recommendations.", "hash": "47d19ea20f55aa5a75b590d259a41386", "id": 8}, {"samples": [{"hash": "3DfTJjpBXuC", "uri": "/contracts/3DfTJjpBXuC#systems-engineering", "label": "Contract Intel 2400 (Intelsat LTD)", "score": 19.0, "published": true}], "snippet_links": [{"key": "the-post", "type": "clause", "offset": [73, 81]}, {"key": "performance-verification", "type": "definition", "offset": [117, 141]}, {"key": "control-center", "type": "definition", "offset": [199, 213]}, {"key": "in-washington", "type": "definition", "offset": [214, 227]}], "size": 1, "snippet": "Participation of at least one subsystem specialist for each subsystem in the post-launch bus subsystems checkout and performance verification. These tests will be conducted from the INTELSAT Mission Control Center in Washington, D.C.", "hash": "ff5fd1fa7019484ca8e79b7aaebcb099", "id": 9}, {"samples": [{"hash": "9OMDqjZelGq", "uri": "/contracts/9OMDqjZelGq#systems-engineering", "label": "Contract", "score": 30.0990098364, "published": true}], "snippet_links": [{"key": "the-contractor-shall", "type": "clause", "offset": [0, 20]}, {"key": "development-of", "type": "clause", "offset": [70, 84]}, {"key": "formal-processes", "type": "clause", "offset": [134, 150]}, {"key": "design-and-development", "type": "clause", "offset": [228, 250]}, {"key": "the-development", "type": "clause", "offset": [283, 298]}, {"key": "associated-documentation", "type": "definition", "offset": [328, 352]}, {"key": "integrated-systems", "type": "clause", "offset": [357, 375]}, {"key": "systems-integration", "type": "clause", "offset": [420, 439]}], "size": 1, "snippet": "The Contractor shall perform systems engineering for the research and development of technical projects. The Contractor shall utilize formal processes that have been developed utilizing a systems engineering approach to project design and development. The Contractor shall assist in the development of systems architectures and associated documentation for integrated systems, specifically aircraft avionics and mission systems integration.", "hash": "040e0caf5705a48219f290fab39867f5", "id": 10}], "next_curs": "ClwSVmoVc35sYXdpbnNpZGVyY29udHJhY3RzcjgLEhZDbGF1c2VTbmlwcGV0R3JvdXBfdjU2IhxzeXN0ZW1zLWVuZ2luZWVyaW5nIzAwMDAwMDBhDKIBAmVuGAAgAA==", "clause": {"parents": [["requirements", "Requirements"], ["entire-agreement", "ENTIRE AGREEMENT"], ["equipment", "Equipment"], ["ordering-period", "Ordering Period"], ["systems-engineering-supporting-activities", "Systems Engineering Supporting Activities"]], "size": 27, "title": "Systems Engineering", "children": [["", ""], ["general-requirements", "General Requirements"], ["standard-builds", "Standard Builds"], ["operations-support", "Operations Support"], ["infrastructure-standards", "Infrastructure Standards"]], "id": "systems-engineering", "related": [["engineering", "Engineering", "Engineering"], ["reverse-engineering", "Reverse Engineering", "Reverse Engineering"], ["value-engineering", "Value Engineering", "Value Engineering"], ["geotechnical-engineer", "Geotechnical Engineer", "Geotechnical Engineer"], ["no-reverse-engineering", "No Reverse Engineering", "No Reverse Engineering"]], "related_snippets": [], "updated": "2025-07-07T12:36:18+00:00"}, "json": true, "cursor": ""}}