JMR_TD_MSAD_Capstone_BAA_Architect_Call_Final.docx

Architect Call for the Joint Multi-Role Technology Demonstrator (JMR TD) Mission Systems Architecture Demonstration (MSAD) Capstone Demonstration Overarching Broad Agency Announcement (BAA)

Prepared by the US Army Aviation Development Directorate (ADD) to supplement the information contained in the JMR TD MSAD Capstone Demonstration Overarching Broad Agency Announcement (BAA) Table 1: Document Update Record Change Log

1. Initial Release

Table 2: Referenced Documents

Document Name

Table of Contents

Introduction This Call, W911W6-18-R-0007, is issued under Broad Agency Announcement (BAA) Number W911W6-18-R-0006, the MSAD Capstone Demonstration. W911W6-18-R-0006 is referred to in this Call as the Overarching BAA. This Call solicits proposals for the Architect Role for the MSAD Capstone S&T Program. This Call provides the Architect Role specific requirements within the overall program objectives, as well as the instructions, and conditions outlined in the Overarching BAA. Sections in this Call supplement the JMR TD MSAD Capstone Demonstration Overarching BAA amplifying some detail and adding necessary information. Offerors are advised to review the Overarching BAA to provide context to the technical details within this Call.

Architect Detailed Discussion Overview of the Architect Role An independent third party contractor will provide the engineering services defined as the Architect role within the Capstone Demonstration (Overarching BAA section 2.8.9.1), and be responsible for providing architectural subject matter expertise to the Government. This role is the preliminary award to allow initial coordination between the Architect and the Government. The Architect is responsible for the development of architectural products, achieving and maintaining architectural consistency, and representing Government interests in matters that impact the technical and business objectives of the Government within Development Group 1 (DG1) during the Capstone Demonstration.

Objectives The main objective of the Architect is to provide architecture expertise to facilitate the achievement of the Capstone Objectives (Overarching BAA section 2.3), Outcomes (Overarching BAA section 2.4), and Focus Areas (Overarching BAA section 2.6) within the context of the Operational Scenario (Overarching BAA section 2.7). The Architect will develop an Objective Architecture (ObjArch), which will be used to guide and constrain the DG1 Mission System Integrator’s (MSIs) production of a System Architecture (SysArch).

Requirements Consistent with Overarching BAA section 2.8.1, the Architect will not be a MSI or the JCA Product Developer, or a teammate of the MSI or Joint Common Architecture (JCA) Product Developer for the purpose of performing on the Capstone Demonstration. The following requirements represent the scope of the research effort to be funded under this Call.

Technical General The Architect shall provide architectural subject matter expertise to the Government, Joint Common Architecture (JCA) Product Developer, and DG1 MSI participants in a manner that supports the Capstone Objectives, Outcomes, and Focus Areas identified in Overarching BAA sections 2.3, 2.4, and 2.6.

The Architect shall provide advice, assistance, and guidance to the Government in defining and documenting the extent and magnitude of acceptable system modifications that can be performed by a 3rd party integrator.

Architecture Development The Architect shall describe the overarching DG1 approach for using modular design, standards-based interfaces, and widely-supported, consensus-based standards in an Open Architecture Management Plan (OAMP).

The Architect shall develop and document within the OAMP, an ObjArch development process including necessary supporting artifacts, models, analysis, and tooling, which is based on provided GFI.

The Architect shall develop and manage an ObjArch Specification, which contains all requirements pertaining to the ObjArch for DG1, based on the RefArch specification provided as GFI.

The Architect shall communicate and coordinate adherence to the hardware, software, functional, and data architecture requirements with the DG1 MSIs.

The Architect shall communicate and coordinate adherence to the software, functional, and data architecture requirements with the JCA Product Developer (to be used in the development of JCA Product Architectures).

The Architect shall identify and describe, within the ObjArch, each category of architecture (hardware, software, functional, and data) and their respective aspects per the JMR Comprehensive Architecture Strategy (JCAS).

The Architect shall identify and describe the key interfaces for each category of architecture within the ObjArch.

The ObjArch shall incorporate JCA components identified in the GFI. (Note: For the release of this Call, two components are identified - Route Planning and Correlation and Fusion. Others may be added).

The Architect shall develop and document the Objective Architecture (ObjArch), based on provided GFI, for DG1 using text-based and model-based methods.

The Architect shall develop and deliver models necessary to describe the ObjArch to include extending the JCAS and Capstone AADL Modeling Template GFI (.aadl and .eap formats) as well as necessary supporting description and user/guidance documentation.

The Architect shall develop a conformance process based upon the provided GFI that demonstrates conformance of the ObjArch to the Reference Architecture (RefArch), JCA Products to the ObjArch, and of the System Architecture (SysArch) to the ObjArch.

The Architect shall document the conformance process within the OAMP.

The Architect shall coordinate consensus of the conformance process with the MSIs of both DGs and the JCA Product Developer.

The Architect shall execute the process and provide evidence of conformance to the RefArch for the DG1 ObjArch.

The Architect shall review evidence of conformance to the ObjArch for the DG1 SysArchs and provide recommendations to the Government.

The Architect shall review evidence of conformance to the ObjArch for JCA Products and provide recommendations to the Government.

The Architect shall develop, manage, and deliver associated tooling and/or processes pertaining to the collection and assessment of conformance evidence for the RefArch and ObjArch.

The Architect shall develop and document within the OAMP, a configuration management process based upon the provided GFI that addresses change and variation of the JCAS.

Architecture configuration management meetings shall be chaired by the Government, and include as members, the MSIs of DG1 and the JCA Product Developer.

The Architect shall coordinate and lead all architecture configuration management meetings pertaining to DG1.

The Architect shall be responsible for the identification, management, resolution, and reporting of issues pertaining to the JCAS and ObjArch for DG1.

The Architect shall perform root cause analysis of issues and defects pertaining to the JCAS and ObjArch, coordinate such results with the DG1 MSIs and JCA Product Developer, and report findings to the Government.

The Architect shall participate in the development of DG1 SysArchs, and provide subject matter expertise to the DG1 MSIs in the development of their respective SysArchs.

Collaboration The Architect shall develop and document within the OAMP, a collaboration plan for DG 1 that includes roles and responsibilities and any necessary tooling, resources, or artifacts.

The Architect shall develop a Capstone Architecture Centric Virtual Integration Process (ACVIP)/Model Management Plan. This plan will be used to standardize the format of architectural artifacts used during the demonstration. It will also allow the Government to efficiently compare the architectural content of each DG and JCA products.

The Capstone ACVIP/Model Management Plan shall complement the purpose and background provided in the Capstone Demonstration Overarching BAA and ACVIP Handbooks provided as GFI.

The Capstone ACVIP/Model Management Plan shall identify standardized exchange formats to allow efficient exchange of architectural information.

The Architect shall coordinate consensus of the Capstone ACVIP/Model Management Plan between the MSIs of both DGs and the JCA Product Developer.

The Architect shall provide a report that documents a recommended approach and guidance for review criteria pertaining to models and required analysis of those models at specified reviews/milestones.

The review approach and guidance shall complement that outlined in the ACVIP handbooks GFI.

The Architect shall perform modeling and analysis tasks in accordance with the Capstone ACVIP/Model Management Plan in support of the Government’s Model-Based Engineering emphasis and of various in-process reviews, excursions, and as directed by the Government.

The Architect shall develop and document within the OAMP, metrics/indicators associated with the assessment of architectural quality, the sensitivity between architecture requirements/quality attributes and Government Key Business Drivers and other appropriate factors supporting decision making and interpretation of demonstration success.

Safety The Architect shall develop an overarching document outlining Architectural Safety Requirements and Technical Guidance (ASRTG) that describes the architecturally significant safety aspects (hazards, requirements, guidance, and rationale) for DG1 based on the provided GFI.

The Architect shall coordinate the overarching ASRTG with both the JCA Product Developer and the DG1 MSIs.

The Architect shall perform a preliminary hazard assessment using both Systems-Theoretic Process Analysis (STPA) and Aerospace Recommended Practice (ARP) 4761 processes of the functions applicable to the Capstone Scenario based upon the levels identified in the Objective Mission System Definition (OMSD) as provided by the Government as GFI.

The Architect shall derive appropriate ObjArch-level safety requirements (architecturally significant) from the preliminary hazard assessment.

Hazards and ObjArch-level safety requirements shall be documented in the ObjArch. Results and other findings, such as the source of the hazards (process used to identify the respective hazards e.g. STPA or ARP 4761) shall be documented in the ASRTG.

The Architect shall incorporate into the ObjArch, architecturally significant safety aspects of the component and system Airworthiness Qualification Plans (AQPs) applicable to all components and systems of the ObjArch.

The Architect shall coordinate with the MSIs (responsible agents) on the development of the system Airworthiness Qualification Specification (AQS).

The Architect shall coordinate with the JCA Product Developer (responsible agent) on the development of the component Airworthiness Qualification Specification (AQS).

Cybersecurity The Architect shall develop a document outlining Cybersecurity Requirements and Technical Guidance (CSRTG) that describes the architecturally significant aspects (controls, requirements, guidance, and rationale) of Confidentiality, Integrity, and Availability for DG1 based on provided GFI.

The Architect shall coordinate the CSRTG with both the JCA Product Developer and the DG1 MSIs The Architect shall include, within the ObjArch, an architectural pattern/method for managing system (hardware and software) configuration.

The Architect shall include, within the ObjArch, an architectural pattern/method that enables addressing cyber vulnerabilities and Information Assurance Vulnerability Alerts (IAVAs) within 15 days of a vulnerability being identified.

The Architect shall perform the “Select” step of the Requirements Management Framework (RMF) process, and evaluate each technical control based on the levels identified in the OMSD and the control’s applicability to the Capstone Scenario.

The Architect shall select, address, and incorporate the applicable Security Requirements Guidelines (SRGs) and Security Technical Implementation Guides (STIGs) requirements from the https://iase.disa.mil website into the ObjArch.

The Architect shall derive appropriate ObjArch-level (architecturally significant) cybersecurity requirements that support the Capstone Scenario.

The Architect shall document identified cybersecurity controls and requirements in the ObjArch. Other findings and results shall be documented in the CSRTG Cyber Report.

Domain Specific Data Model (DSDM) The Architect shall manage and refine the Government-furnished JMR DSDM.

The JMR DSDM shall be derived from the JCA conceptual data model, and conformant to the FACE Technical Standard, Edition 3.0.

The Architect shall extend the JMR DSDM with logical level content obtained through collaboration with the JCA Product Developer and MSIs as well as from other potential sources of DSDM content.

Excursions The Architect shall collaborate with the Government in the development and refinement of the Capstone Demonstration Excursion Plan.

The Architect shall develop the Excursion Test Plan, which will outline the high level test descriptions that identifies the scope of the verification activities MSIs will be expected to perform to meet Capstone Demonstration objectives.

Lessons/Best Practices The Architect shall develop a “best of breed” Architecture Description Document (ADD) based upon the DG1 and DG2 ObjArch and SysArch products.

The Architect shall consolidate, manage, and report, across both DGs, a summary of the lessons/best practices identified during the execution of Capstone Demonstration pertaining to architecture development (RefArch, ObjArch, and SysArch).

The Architect shall provide recommendations for improvement on GFI (processes, tools, handbooks, resources, etc).

The Architect shall provide a report outlining the recommendations and analysis pertaining to the use and value of the architect role in future procurements, considering the interactions with the other Capstone Roles.

Programmatic General The Architect shall represent the Government’s interests in all matters pertaining to the Government’s business and technical objectives as reflected within the RefArch, ObjArch, and SysArch during the Capstone Demonstration.

Management The Architect shall provide oversight of DG1 architectural tasks and activities.

The Architect shall develop an integrated master schedule (IMS) to level 3 based upon the Government provided schedule in section 2.9 of the Overarching BAA that identifies, at a minimum, development phases, durations, dependencies, and key In-Process Reviews (IPRs).

The Architect shall perform a kick-off meeting within 20 days of contract award.

The Architect shall participate in each of the meetings/reviews indicated in figure 1 below.

The Architect shall coordinate and lead the DG1 kick-off meeting in collaboration with the MSIs and JCA Product Developer.

The Architect shall be responsible for managing the implementation of the JCAS for the Capstone Demonstration.

The Architect shall provide the Government with feedback and revision recommendations pertaining to the JCAS and its implementation.

The Architect shall implement and deliver revisions to the JCAS, approved by the Government, based on feedback from DG1 and DG2. Revisions shall include an updated RefArch.

The Architect shall develop a “Users Guide” that incorporates a set of recommended best practices for the use of the JCAS.

The Architect shall initiate NDAs with Capstone Demonstration participants within 10 working days of being informed of its necessity. NDAs shall be completed within 30 working days of initiation. Notification of completion shall be reported to the USG contracting officer.

The Architect shall provide monthly Technical Status Reports (TSR) detailing technical progress.

Monthly TSRs shall describe work performed to date, by task, compared to the work plan, including schedule status; and report on all problems and suggestions for improving provided GFI (tools, processes, artifacts, etc), technical issues or major developments during the reporting period.

Monthly TSRs shall provide a brief summary of results and findings and an assessment of all data, findings, lessons learned, and conclusions as a result of each subtask effort as well as plans for the next reporting period. Additionally the TSR shall report the use of metrics identified in the OAMP.

The Architect shall provide monthly Cost Status Reports (CSR) detailing cost, schedule, and staffing.

Monthly CSRs shall describe schedule, status of deliverables, funding levels (planned vs actual), and staffing progress (hiring status, number of full time equivalents, and hours expended (planned vs actual)).

Monthly CSRs shall compare task progress to the plan, explain any variance exceeding 10%, and include an overview of progress as well as funding levels and variances.

Program Data Repository The Architect shall establish a repository of program information that protects intellectual property (IP) and reports cyber incidents in compliance with DFARS 252.204-7012/NIST SP 800.171 for all Covered Defense Information (CDI). All information associated with the Capstone Demonstration is considered CDI.

The Architect shall develop an OPSEC Plan per AR530-1.

The Architect shall use the Government specified collaboration service (e.g. Army Knowledge Online, or other repository TBD), to distribute information and collaborate with Capstone Demonstration Participants.

If directed, the Architect shall obtain Public Key Infrastructure (PKI) tokens supporting two factor identification for personnel assigned to this task within 20 days of being provided instruction.

Meetings/Travel The Architect shall support the expected meetings identified in figure 1 below.

Figure 1 Expected Meetings/Reviews

* For planning purposes only. Location will likely vary ** For planning purposes, duration is anticipated length of actual meeting. Include additional days for travel as appropriate.

Funding Level, Performance Period, and Order of Precedence.

Any award made from this call will be subject to availability of funds. The Government plans to incrementally fund efforts starting in FY18, with additional funding being provided in FY 19 and FY 20.

The Period of Performance for the Call is expected to begin in 4QFY18 and continue to the end of 1QFY21.

Any inconsistency in this Call and the Overarching BAA shall be resolved by giving precedence to the language stated in this Call.

Funding Instrument See section 4 of the Overarching BAA.

Security Requirements See section 5 of the Overarching BAA.

Government Furnished Data / Equipment / Information The information identified in this section reflects content that is made available to the Architect for the purpose of establishing the Capstone ObjArch (Overarching BAA section 6). Content format and distribution limitations are identified in the table below.

Capstone Operational Scenario (included as part of JCAS model)

JCAS

Model Architecture Requirements Comprehensive Architecture Strategy

D/ITAR

.eap/.html .xls .docx Proposal

Joint Common Architecture (JCA) (included as part of JCAS model)

Objective Mission System Definition (OMSD) (included as part of JCAS model)

* GFI is maturing and will continue to mature during the Capstone effort. “Proposal” indicates a draft will be provided with the release of the Overarching BAA/Call. “Award” indicates a draft will be provided at award. Any revisions to provided GFI will be available upon Award.

Instructions to Offerors General The following sections identify the volumes and their contents that will contain the information presented in the Offeror’s response. They are listed in order of importance.

PROPOSAL VOLUME I – Technical Approach:

Consistent with section 7.2 of the Overarching BAA, the Technical Volume is composed of a textual description of the Offeror’s approach, and a model-based draft of the ObjArch that is separate from, but complementary to, the written description. The page count of the textual description will be limited to 28 pages inclusive of the Data Rights Sub-Factor. The Government will assess the Offeror's technical approach for satisfying the following items, which are listed in order or precedence:

1. The Offeror shall describe the approach to accomplishing the requirements set forth in section 2.3 of this Call, and specifically address the approach to:

a. Providing architectural subject matter expertise to the Government and Capstone Demonstration industry participants in a manner that supports the Capstone Objectives, Outcomes, and Focus Areas identified in sections 2.3, 2.4, and 2.6 of the Overarching BAA respectively.

b. Development of the architecture outlined in 2.3.1.2 of this Call including the products, requirements, plans ,tools, processes, and use of Government Furnished Information.

c. Collaboration and coordination of the ObjArch and its products, requirements, plans, tools, processes, and use of Government Furnished Information as outlined in 2.3.1.3 and 2.3.2.3 of this Call.

d. Developing the lessons and best practices identified during the Capstone Demonstration as well as producing a “best of breed” architecture definition as outlined in section 2.3.1.8 of this Call.

e. Performing a hazard assessment using both STPA and ARP 4761, deriving appropriate ObjArch-level safety requirements, and the manner in which safety is incorporated as an architecturally significant requirement as outlined in 2.3.1.4 of this Call.

f. Performing analysis, deriving appropriate ObjArch-level cybersecurity requirements and patterns, and the manner in which cybersecurity is incorporated as an architecturally significant requirement as outlined in 2.3.1.5 of this Call.

g. Managing the technical execution of this Call, representing the Government’s interests, and in particular the implementation and management of the JCAS as outlined in 2.3.2.1.1 and 2.3.2.2 of this Call.

h. Developing the Capstone Demonstration Excursion Plan and Test Plan as outlined in 2.3.1.7 of this Call.

i. Managing and Refining the JCA DSDM as outlined in 2.3.1.6 of this Call.

2. The Offeror shall develop a draft example of an ObjArch by extending the JCAS and Objective Mission System AADL template GFI in a manner that complements and reinforces the written technical approach. The draft ObjArch is not intended to be complete, but rather to communicate the Offeror’s understanding of the Government’s intent for a model-based representation of an ObjArch. The draft ObjArch communicates the proposed modeling approach in a model-based format informed by the Government. The draft ObjArch shall be based on the following:

a. The Offeror shall extend the JCAS model (provided as GFI in .eap format) by developing a draft of a functional architecture that supports the Capstone Operational Scenario, and includes a representative sample of identified common and specific platform functions.

b. The Offeror shall extend the Functional Architecture to a logical level and include the use of the Capstone AADL Modeling Template (provided as GFI in .aadl format) consistent with the “Refinement 1” example. This modeling exercise (2a. and 2b.) is intended to demonstrate the Offeror’s understanding of the Government’s intent and serve as an example method for conveying the Offeror’s technical approach using model-based methods.

3. The Offeror may describe the approach to any other item that is relevant to the Objectives, Outcomes, or Focus Areas, identified in sections 2.3, 2.4, or 2.6 of the Overarching BAA respectively.

PROPOSAL VOLUME I Sub-Factor – Data Rights In accordance with Table 2 of this Call, the Government desires, “Unlimited Rights”, but requires at a minimum, "Government Purpose Rights" (GPR) as defined by DFARS Part 227, to all technical data, deliverables, and computer software developed under this Call, and no limitations on the use of delivered and/or residual hardware, exempting background data assertions. It is the Offeror's responsibility to clearly define in the proposal, the proposed data rights for technical data, computer software and each deliverable. Ambiguities will be negatively evaluated against the Offeror. Background data and software (possessing less than GPR data rights) shall not be coupled to data, deliverables, and software developed under this Call. Approaches that make use of background data should be carefully considered given the Government’s intent, and should provide a method to allow continued use in subsequent Government activities (to include use by Government contractors), or support a clear and achievable path to alternative processes and tools. The Government will assess the Offeror’s approach to Data Rights as they pertain to the following items, which are listed in order or precedence:

1. The Offeror shall describe the approach to providing the Government with desired GPR or greater data rights for produced architectural artifacts.

2. The Offeror shall describe, when appropriate, the approach to ensuring that tools and processes proposed with Limited Rights are not coupled to required deliverables possessing GPR or greater data rights.

3. The Offeror shall describe, when appropriate, the approach to allowing the Government (and Government contractors) the continued use of tools and processes possessing Limited Rights during subsequent Government efforts.

4. The Offeror shall describe any software it will assert Restricted Rights or commercial license rights, and how it will facilitate licensing for this software to support the BAA objectives. In addition, the Offeror will include copies of any commercial software licenses/end user licensing agreements (EULAs) that will require the Government to agree to either with the Offeror or one of its suppliers.

PROPOSAL VOLUME II - Technical Experience and Qualifications Consistent with the instructions and page count indicated in section 7.3 of the Overarching BAA, the Government will assess the Offeror's experience and qualifications as they pertain to the following items, which are listed in order or precedence:

1. The Offeror shall describe previous experience in leading highly collaborative projects requiring high levels of subject matter expertise in order to create overarching products that must attain consensus prior to implementation.

2. The Offeror shall describe previous experience with developing, describing, and managing architecture to include the application of open system architectures and Modular Open Systems Approach (MOSA) in a relevant domain (e.g. aviation, maritime, or automotive).

3. The Offeror shall describe previous experience deriving product line architecture from an established enterprise architecture.

4. The Offeror shall describe previous experience establishing conformance (or compliance) procedures as well as assessing conformance to one or more architectural standards.

5. The Offeror shall describe previous experience with system and software development security as well as experience with applying lessons gained through methods such as penetration testing to improve cyber security.

6. The Offeror shall describe previous experience with the identification and use of metrics/indicators in the assessment of how well a product exhibits desired characteristics. Emphasis should be placed on applicability to architecture and other similar abstractions.

7. The Offeror shall describe previous experience with performing hazard assessments, deriving architecturally significant safety requirements, and describing those requirements in a model-based format.

8. The Offeror shall describe previous experience with ACVIP processes and tools, or the manner in which a suitable level of experience (supportive of the technical approach) will be gained, prior to award.

9. The Offeror shall describe previous experience with STPA processes, or the manner in which a suitable level of experience (supportive of the technical approach) will be gained, prior to award.

10. The Offeror shall describe previous experience with model based processes and tooling supporting architecture development, exchange of model-based information, and virtual integration.

11. The Offeror shall identify key personnel to include a Lead Architect, and the approach to managing key personnel.

12. The Offeror shall describe the suitability (experience, qualifications and availability) of identified key personnel performing the proposed work, and of the Lead Architect in particular. Key personnel shall have at least 10 years of experience performing architecture development in a relevant environment. Biographies shall be provided for key personnel.

13. The Offeror shall describe any existing or planned business relationships as they pertain to section 2.8.1 of the Overarching BAA.

14. The Offeror shall describe the suitability and availability of the work environment (facilities, processes, tooling, etc) supporting the proposed work.

PROPOSAL VOLUME III - Cost Consistent with section 7.5 of the Overarching BAA, the Government will assess the Offeror's cost approach as they pertain to the following items, which are listed in order or precedence:

1. The Offeror shall include specific details that demonstrate the Offeror's understanding of proposed costs.

2. The Offeror shall indicate the proposed funding instrument (e.g., TIA, FAR-based contract, OT, etc.). Any proposed cost share will be calculated as follows: contractor cash plus in-kind contribution divided by project value. Any resulting agreement value will exclude the Offeror’s “sunk” costs of prior research as cost match.

3. The Offeror shall include a funding profile (a cost breakout by month), a cost breakdown providing man-hours and monthly costs by task, all pricing rates used, travel and equipment and materials listings, if applicable.

4. In accordance with section 7.4 of the Overarching BAA, the Offeror shall ensure that all subcontracted work must be appropriately identified as such and that cost proposals by each subcontractor/sub recipient are included in the proposal or that the subcontractor submits a detailed proposal concurrent to the Government with the Offeror’s submission.

5. The Offeror shall provide sufficient details to demonstrate the cost reasonableness and realism of the proposed cost approach. Such details will include the basis for estimating proposed costs, and sufficiently explain estimating processes, methods, factors as well as any assumptions or contingencies used in the proposed cost estimates. The cost approach should complement and support the technical approach.

PAGE LIMITATIONS

The limitations set forth in section 7.5 of the Overarching BAA, for page count and delivered model formats will be applied; therefore the Evaluators will not evaluate any content in pages beyond the page limit or in noncompliant model content.

Evaluation Criteria / Basis for Award Consistent with section 8 of the Overarching BAA, the Evaluation Factors identified in the sections below are listed in order of evaluation precedence (most important to least important).

Proposal Submission Instructions Technical and cost proposals shall be provided in electronic format. The cost proposal shall be provided in the offerors format as well as Excel format for cost verification purposes. Proposals shall be submitted via AMRDEC Safe Access File Exchange (SAFE): https://safe.amrdec.army.mil/safe/ to AATD/ADD, Attn: CCAM-RDT, Hope McClain, Bld. 401 Lee Blvd., Fort Eustis, VA 23604-5577; hope.a.mcclain.civ@mail.mil. Further proposal submission instructions will be included in a letter sent to offerors invited to submit full proposals. Proposals shall be received not later than 19 April 2018; 1630 eastern time.

Questions may be submitted in writing via email to Hope McClain, hope.a.mcclain.civ@mail.mil. All questions must be submitted no later than 14 days prior to the call closing date to ensure a response. All substantive questions and responses received which can be answered without revealing sensitive information will be posted to FedBizOpps as an amendment to the call. White Papers and Proposals received after the date and time specified for closing will be handled in accordance with the Overarching BAA.

Evaluation Factor I - Technical Approach Consistent with section 8.2 of the Overarching BAA, the Government will assess the Offeror's response to the items, identified in section 7.2 of this Call. The Government will evaluate the Offeror’s response against the following considerations:

1. Sufficiency of the Offeror’s response to satisfy the requirements of this Call and the Overarching BAA Capstone Objectives, Outcomes, and Focus Areas.

2. Likelihood of the Offeror’s response to satisfy the requirements of this Call and the Overarching BAA Capstone Objectives, Outcomes, and Focus Areas.

3. Consistency and alignment between the written technical response and the model-based response of the draft ObjArch, and the depth and usage of the model-based draft ObjArch to convey intent and understanding of the Government’s objectives.

4. Sufficiency of the Offeror’s approach to:

a. provide desired data rights supporting the requirements of this Call, the Capstone Objectives, Outcomes, and Focus Areas identified in the BAA.

b. to decouple (where appropriate) developed architectural products from any used processes and tools that may possess Limited Rights.

c. to provide (where appropriate) the Government and its contractors with the opportunity to continue the use of resources possessing Limited Rights in subsequent Government efforts.

5. Degree to which the Offeror’s approach to data rights is consistent with, and supportive of, the technical approach.

Evaluation Factor II - Technical Experience and Qualifications Consistent with section 8.3 of the Overarching BAA, the Government will assess the Offeror's response to the items, identified in section 7.3 of this Call. The Government will evaluate the Offeror’s described experience and qualification in the context of time (within the last 5 years) and relevance (directly pertaining to an aviation or similar domain) for the following considerations:

1. Relevance of the Offeror’s described experience and qualifications.

2. Amount of Offeror’s relevant experience.

3. Suitability of key personnel performing the proposed work.

4. Degree to which experience, key personnel and facilities are consistent with, and supportive of, the Offeror’s technical approach.

5. Likelihood of the Offeror’s experience to satisfy the requirements of this Call, and the Overarching BAA Capstone Objectives, Outcomes, and Focus Areas.

Evaluation Factor III - Cost to the Government Consistent with section 8.4 of the Overarching BAA, the Government will assess the Offeror's response to the considerations identified in section 7.4 of this Call. The Government will evaluate the Offeror’s response for the following considerations:

1. Overall value to the Government of the proposed effort.

2. Reasonableness of the proposed cost.

3. Realism of the proposed man-hour, material, and other costs to accomplish the proposed effort (see FAR 2.101 - Definitions, Cost Realism). Costs to the Government of any required GFE / GFI or facilities will also be included in the evaluation.

4. Degree to which the cost approach is consistent with, and supportive of, the proposed technical approach, experience and data rights.

5. Likelihood of the Offeror’s response to satisfy the requirements of this Call, and the Capstone Objectives, Outcomes, and Focus Areas identified in sections 2.3, 2.4, and 2.6 of the Overarching BAA.

Data Items / Deliverables Deliverables for this Call are identified in the table below.

Table 2 - Architect Deliverables

2.3.1.2.4.1 2.3.1.2.5 2.3.1.3.1 2.3.1.3.5 Unlimited

2.3.1.4.3 2.3.1.5.6

Unlimited

2.3.1.4.4 2.3.1.5.2 2.3.1.5.3 Unlimited

2.3.1.2.4.4 2.3.1.2.4.5 Unlimited

Conformance Tooling

2.3.2.2.2.1 2.3.2.2.2.2 2.3.2.2.2.3 Unlimited

2.3.2.2.2.1 2.3.2.2.2.2 2.3.2.2.2.3 Unlimited

image1.emf