Loren Data's FBO Daily™

Home Today's FBO Search Archives Numbered Notes CBD Archives Subscribe

A -- Market Research to refine the composition and data content of the Joint Common Architecture (JCA) model as part of the Joint Multi-Role Technology Demonstrator (JMR TD) program.

Notice Date
Notice Type
Sources Sought
541511 — Custom Computer Programming Services
Contracting Office
ACC-RSA-AATD - (SPS), ATTN: AMSRD-AMR-AA-C, Building 401, Lee Boulevard, Fort Eustis, VA 23604-5577
ZIP Code
Solicitation Number
Response Due
Archive Date
Point of Contact
hope mcclain, 757-878-2993
E-Mail Address
Small Business Set-Aside
Request for Information: This is a Request for Information (RFI) as defined in FAR 15.201(e). This request is for planning purposes only and shall not be considered as an invitation for bid, request for quotation, request for proposal, or an obligation on the part of the Government to acquire any products or services. Your response to this RFI will be treated as information only. No entitlement to payment of direct or indirect costs or charges by the Government will arise as a result of contractor submission of responses to this announcement, or the Government use of such information. The US Army Aviation and Missile Research Development and Engineering Center (AMRDEC) is conducting market research to refine the composition and data content of the Joint Common Architecture (JCA) model as part of the Joint Multi-Role Technology Demonstrator (JMR TD) program. Procurement of multiple JCA conforming subsystems and components is anticipated as part of the Joint Multi-Role Technology Demonstrator Phase 2 Program. 1.0Background: In October 2011, the Deputy Secretary of Defense issued the Future Vertical Lift (FVL) Strategic Plan to outline a joint approach for the next generation vertical lift aircraft for all Military Services. The strategic plan provides a foundation for replacing the current fleet with advanced capability by shaping the development of vertical lift aircraft for the next 25 to 40 years. The strategic goals of the plan requires transformational vertical lift capabilities, maximization of resources through commonality among platforms, and preservation and continued development within government, industry, and academic Science and Technology (S&T) communities. Additionally, The Office of the Secretary of Defense (OSD) vision for FVL is to employ commonality where appropriate to reduce costs, and more efficiently allocate resources. The AMRDEC is currently developing an open systems architecture (OSA) definition for the FVL Family of Systems (FoS) under the JCA S&T effort. JCA is following the Modular Open Systems Approach (MOSA) principles and leveraging existing and emerging OSA related efforts (including the Future Airborne Capability Environment (FACETM) consortium). JCA in its final form will comprise a model, guidance documents and an ecosystem. The JCA model represents a collection of existing widely used and Industry-accepted standards, the reference architecture, and supporting documentation. The JCA Reference Architecture is a conceptual framework identifying a set of avionics subsystems, avionics components, their interfaces, their allocated functionality, common semantics and composition rules at the Domain, Subsystem, and Component Levels. JCA defines the reference architecture to a level sufficient to guide the transformation of FVL avionics development and delivery from an approach that is aircraft mission specific to an approach that maximizes the reuse of avionics systems (subsystems) and software (components) across the FVL FoS. JCA will be exercised and validated during the AMRDEC's Joint Multi-Role Technology Demonstrator Phase 2 effort prior to implementation by FVL. Operational and functional requirements guiding JCA development were derived from the Army's Aviation Operations Capabilities Based Assessment (CBA), the Army's Aviation Survivability CBA, the Army sponsored FVL FoS Initial Capabilities Document (ICD), and the OSD FVL Concept of Tactical Employment (COTE), with initial emphasis on Army requirements ( quote mark Top Down quote mark ). Additionally, JCA content was derived from an analysis of current avionics systems and software ( quote mark Bottom Up quote mark ). JCA is being developed to allow for efficient scaling to include other Armed Service's FVL requirements. AMRDEC plans to collaborate with representatives from the Air Force, Navy (anticipated prior to the end of FY13), Marine Corps, Homeland Security, Coast Guard, and Special Operations community in the future. FVL multi-role capabilities enabled by avionics will support a wide range of joint missions (Army specific missions underlined in Attachment 1, Table 2-1), including aerial reconnaissance, anti submarine warfare (ASW), Anti Surface Warfare (ASUW), special operations, amphibious assault, undersea warfare, surface warfare, air assault, Medical evacuation (MEDEVAC), Intelligence Surveillance Reconnaissance (ISR), Search and Rescue (SAR), Command and Control (C2), Combat Search and Rescue (CSAR), attack, logistics, homeland security and cargo operations. JCA will support Army affordability goals by guiding the reuse of technically mature avionics and avionics software, reduction of duplicative avionics development, reduction of redundant avionics testing, and simplification of avionics integration and certification. The AMRDEC believes that FVL designs and implementations will follow a Model Based Development (MBD) approach so JCA has adopted the constructs defined by the Open Management Group's (OMG) Model Driven Architecture (MDA). All JCA information is captured in a (computing) platform independent model (PIM). Employment of an MDA approach will allow efficient reuse of JCA data by FVL Program Management Offices, FVL Avionics product suppliers, and airworthiness certification authorities. The AMRDEC joined the FACE Consortium in 2010 as a founding member with the intent to gain industry participation in the development of JCA. RFI responders are encouraged to download and review the latest FACE documents at www.opengroup.org/FACE/published-documents. 2.0RFI Objectives: This RFI serves as the initial opportunity for industry to participate in the refinement of the contents of the JCA prior to JMR TD Phase 2 effort. Conformance to JCA is anticipated for JMR TD Phase 2 avionics systems demonstrations. Any information received in response to this RFI may be utilized on a non-attribution basis. The Government intends to issue a follow-on RFI once all information has been received and analyzed in order to provide industry with the details of any resulting modifications made to the JCA model's composition / data content and to solicit further comments. 3.0Information Requirements: In order to mature JCA from its current state to its desired state to support FVL, the plan is to establish a JCA Working Group (WG) consisting of both Government and Industry Subject Matter Experts (SME). The JCA WG will be responsible for establishing and documenting JCA domains, subsystems, components, and interface standards. The JCA WG will also conduct a reusability assessment by applying constraints such as safety, security, system performance, business model considerations. AMRDEC is requesting the following information: 3.1 Domains (attachment). A. Recommended additions, consolidations, or deletions with corresponding rationale to the list of Domains in Table 2-5. B. Recommended definition changes to the Domains. C. Comments on the approach used to develop the JCA Domains: The Domains were the result of applying the following rules: (1) Where there is a clear use of a domain (title, definition) among all current Army aviation platforms, reuse it; (2) Application of Air Transport Association (ATA) Chapter headings and definitions (3) Develop avionics domains to reflect/align with DO-297 Integrated Modular Avionics and the grouping of avionic subsystems into quote mark effectors quote mark and quote mark sensors quote mark. 3.2 Subsystems (attachment). A. Recommended additions, consolidations, or deletions to the list of subsystems (along with corresponding rationale) in Table 2-2 JCA Subsystems. A potential example of combining multiple subsystems into a single subsystem would be the combining of the ADS-B subsystem with the IFF subsystem resulting in a single subsystem titled IFF, but whose definition encompasses both ADS-B and IFF. B. Recommended changes to assigned titles and/or definitions for the subsystems in Table 2-3. JCA Subsystem titles are intended to be vendor neutral and identify conceptual subsystems; not a specific vendor's product. C. Identification of other subsystems that are currently being reused but are not highlighted. See Figure 2-1: JCA Subsystems (highlighted in grey area). D. Identification of other subsystems in Figure 2-1 that are not highlighted but could/should be considered for reuse in the FVL FoS. E. Advantages / Disadvantages of including Flight Controls (outer loop subsystems and components) into the scope of JCA. F. Advantages / Disadvantages of including the subsystem located on the ground (Ground Control Station) to enable optionally piloted capability into the scope of JCA. 3.3 Components (attachment). A. Recommended additions, consolidations, or deletions to the list of components allocated to a General Purpose Processor (GPP) subsystem in Figure 2-2: JCA Components allocated to FACE portable Component Segment and Figure 2-3: JCA Components allocated to FACE Platform Specific Segment. B. Recommended changes to the assigned names and/or definitions for the components in Table 2-3 JCA Components. C. Recommended changes to the assigned FACE segment (PCS or PSS) in Figure 2-2: JCA Components allocated to FACE portable Component Segment and Figure 2-3: JCA Components allocated to FACE Platform Specific Segment. D. Advantages / Disadvantages / Risks of establishing a Software Product Line (SPL) for the FVL FoS to enable reuse among multiple, unique GPP's developed by multiple vendors by mandating conformance to the FACE Technical Standard as opposed to planning to reuse the identical GPP subsystem across the FVL FoS. E. Advantages / Disadvantages / Risks of not including a reusable FACE TSS component or a reusable FACE OSS component and the ability to reap the benefits of a SPL. 3.4 JCA Model Working Group (WG). Advantages / Disadvantages / Ability of the FACE Consortium to serve as the Government - Industry body to develop the composition / data content of the JCA Model. 4.0Format Requirements: 4.1 This is a market research announcement for informational and planning purposes only and does not constitute a Request for Proposal, nor is it to be construed as a commitment by the Government. The Government does not intend to award a contract on the basis of this RFI or to pay for any information, or otherwise reimburse responders for any costs associated with their respective submissions in response to this RFI. All submissions will be treated as information only. Respondents will not be notified of the results of any review of this RFI; however, clarification of submissions may be requested by the Contracting Officer. Participation in this effort is strictly voluntary. 4.2 Notional response expectation is 40 pages or less. A corporate capability brief may be included as an attachment, but should not exceed five (5) typed pages. This attachment will not be counted against the response page limitation. AMRDEC is interested in obtaining responses to the questions posed in section 3 above. Please do not send information on specific products. 4.3 Responses to this RFI are requested by close of business 15 July 2013. Unclassified responses should be submitted electronically via the AMRDEC Safe Access and File Exchange website (https://safe.amrdec.army.mil/SAFE/) in Microsoft Office format or as a portable document format ( quote mark.pdf quote mark ) file. Use the following email address as prompted by the site: hope.a.mcclain.civ@mail.mil. If proprietary or copyrighted information is submitted, please include a statement authorizing the Government to copy and use it within the Government for evaluation purposes. Appropriately marked proprietary information will be properly protected by the U.S. Government. Classified information should not be submitted. AMRDEC's SAFE site is not approved for transmission of classified information. The contracting point of contact is Ms. Hope McClain, Bldg 401 Lee Blvd, Fort Eustis, VA 23604-5577, (757) 878-2062, hope.a.mcclain.civ@mail.mil.
Web Link
FBO.gov Permalink
Place of Performance
Address: ACC-RSA-AATD - (SPS) ATTN: CCAM-RDT, Building 401, Lee Boulevard Fort Eustis VA
Zip Code: 23604-5577
SN03080878-W 20130607/130606001723-0ed319f23d988333e3577e0144b2e6cf (fbodaily.com)
FedBizOpps Link to This Notice
(may not be valid after Archive Date)

FSG Index  |  This Issue's Index  |  Today's FBO Daily Index Page |
ECGrid: EDI VAN Interconnect ECGridOS: EDI Web Services Interconnect API Government Data Publications CBDDisk Subscribers
 Privacy Policy  © 1994-2016, Loren Data Corp.