Amendment_1_-_BAA_Call_W911W6-R-0013_JMR_MSAD_Capstone_-_SSoT.pdf

Amendment 1: BAA Call W911W6-R-0013 –

Revised Proposal Submission Instructions and Questions and Answers

Revised Proposal Submission Instructions:

Proposal Submission Instructions Technical and cost proposals shall be provided in electronic format. The cost proposal shall be provided in the offeror’s 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 hope.a.mcclain.civ@mail.mil, raymond.h.wall2.civ@mail.mil, and to william.j.jacobs16.civ@mail.mil. Proposals shall be received no later than 24 June 2019; 4:00pm eastern time.

Questions may be submitted in writing via email to Rob Waible, robert.c.waible.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.

Proposals received after the date and time specified for closing will be handled in accordance with the Overarching BAA.

NOTE: Previously, proposals were being submitted to Rob Waible. Please do not send to Rob Waible as he will be out of office and cannot receive proposals! In addition, advise all offerors submitting proposals to follow up with an email to Hope McClain to ensure that the proposal was received.

Questions and Answers:

1. What is the expected period of performance for each of the three phases? Response: Dates below are for planning purposes, and the Offeror should feel free to adjust as appropriate to their technical approach.

Response Phase 1 ends ~ 27 April 20 (~100 days) Phase 2 ends ~ 16 Oct 20 (~120 days) Phase 3 ends ~ 15 Dec 20 (~40 days)

2. As mentioned in sections 2.1 and 2.3.1, what is the Government’s intent for a high degree of tooling and automation?

Response: The Government's intent is that to the extent possible, tooling and automation either performs or supports much of the ASoT functionality. Model import and translation, discovery of information, and the ability to identify and follow the https://safe.amrdec.army.mil/safe/ mailto:hope.a.mcclain.civ@mail.mil mailto:raymond.h.wall2.civ@mail.mil mailto:william.j.jacobs16.civ@mail.mil mailto:robert.c.waible.civ@mail.mil relationships between managed content are examples of ASoT features that would benefit from high degrees of tooling or automation. Additional examples would be management and dashboard features that provide change information, trending, and other useful metrics from a technical or programmatic perspective. Essentially, the automation and tooling assists the human in understanding and using the vast amount of related information that will be contained within the ASoT

3. Please provide specific examples of models in reference to Figure 1 of the call.

Response: The below is provided as context and is not considered to be definitive.

The purpose of the study is to identify the types of managed content and to elaborate on the relationships between the content.

System Models: Models and artifacts describing system structure and behavior (e.g.

SysML, UML)

Product Support Models: Models and artifacts describing how the system works or how the user interacts with the system. Interactive training and manuals are examples. Process models (e.g. BPMN) are also included in this type.

Specialty Engineering Models: Models and analysis supporting specific questions/niche analysis such as finite element, fluid and flow models, as well as possibly simulation models (e.g. survivability and environmental impact etc)

Management Models: Models and artifacts supporting management activities that include process models (e.g. BPMN ), cost and other parametrics, schedule, etc.

Design Models: Models and artifacts that provide system description and design details (e.g. SysML, UML, executable specification, Simulink SCADE, CATIA/CAD, etc).

Manufacturing Models: Models and artifacts that include parts, part numbers, BOM, sources, and establishes links to costing and purchasing databases. Likely includes links to PLM tools. Includes process models (e.g BPMN), and production parametrics that support efficiency, cost and duration metrics.

Verification and Validation Models: Models and artifacts that describe test files, test harnesses, test environment, interfaces as well as models of test components using SysML, UML, AADL, and parametrics. Possesses relationships to requirements and possibly formal languages to translate tests and requirements into auto generated system code. Models are incremental and compositional and describe instrumentation and calibration of managed test content. May also include simulation models (e.g. VBS, FLAMES, etc).

4. Does the Government intend to have the controlling authority to manage software changes to the ASoT or Supplier data change incorporation into the ASoT?

Response: While the Government does not yet have a position on this question, a major concern is being vendor locked into a particular tool or set of tools, or being forced to make a change that has wide ranging impacts without appropriate awareness/agreement. The Government would prefer this question to be addressed as part of the study and provided as a recommendation.

Proposal Submission Instructions