Attach 2 - EA Industry Day Feedback.xlsx

What's First
Challenges
Value
Best Practices
Collaboration
Improve communications to break down cultural barriers
Leverage existing capabilities and solutions
Culture
Tools (DEVSECOPS)
Security
Shift culture to one of an improved collaboration vs individual program perceived risk
Improve decision making and data sharing for IRAD and prototypes
Training / Professional Development
Processes (GOVERNANCE)
DevSecOps/Software Architecture
Enhance information sharing on both legacy and new programs
Streamline sharing of artifacts, models, and feedback enable transparency
Empowerment
People (CULTURE)
EA Attributes
Strive to balance innovation against the not invented here attitude
Leadership Buy-In
Standards (KEY ELEMENTS)
Enhance speed to adapt to new technology rapidly in order to remain relevant
Sharing and Feedback Processes
Flexibility for Change
First Steps
Choose tools that are available and are equally effective for both large and small organizations
Improve scalability and flexibility of infrastructure
Common Accessible Environment
CONTRACTING
Provide Government DevSecOps tools to all, in order to reduce the barrier to entry
Common enterprise architecture to centralize processes and protocols
Collaboration Tools / Open Source
OTHER
General Comments
Enforce data controls
Improve integration efficiency through synchronization of efforts
Establish a Standards Working Group
Agile Contracting
Industry is a stakeholder in contributing to developing open, accessible transparent approaches
Leverage Industry / DoD existing Standards
Development Kits (GFE)
Standards Flexibility and Governance
Emplace controls enabling industry-to-industry collaboration
Facilitate easier technology transition get out of valley-of-death
Improvement oriented Processes (Adaptive / Process Improvement)
Develop Enterprise architecture that is inclusive / considers contractor technical approaches
Documentation of Processes
Develop agile processes for Enterprise Architecture (agile is not just for software)
Incorporate agile process into the business and governance
Provide value proposition, strategy, roadmaps enabling industry to transition from old tools and processes and adopt modern, more effective ones
Allow industry/market to drive share with ALL
Incentivize Stakeholders
Encourage, enable, promote, facilitate small business entry and sustainment with DoD
Protect data rights and proprietary solutions
Promote diversity in contract vehicles
Reduce total ownership costs and timelines
Understand and develop process/protection of data privacy as technology matures/advances
Strengthen data rights strategy to avoid delays/roadblocks
CI/CD Pipelines account for newer extended reality s/w languages and devices.
Focus on what or how first. Not both.
Rapid ATO and embedded certificate to field approvals for multi-vendor platform application.
No outliers: All have a place in the EA, Include all aspects from beginning.
Use a models based approach to architect.
Authority to police the data model: Prohibit random new proprietary data, Force data commanality, STRI to be the referee.
Define technical/operational architecture. Components need to be cohesive loosely coupled clean interfaces, Precondition for all else to matter or be coherent.
CI/CD Pipelines account for newer extended reality s/w languages and devices.
Common framework for functionality development, Standard methodoligies to develop/maintain interoperability, Centralized model/repository.
What is the baseline you're going to measure against to gauge EA solution, "Know what you have."
Structure for capturing and processing human performance data.
For a working group, interoperability, would be #1 to figure out a standard. The IMO AAR commons is key.
Common understanding of information-data model.
STRI or someone to police and compile a library of data types.
No unnecessary new data types.
Shared, free data model.
Common software factory.
Solution Architecture [Needs/PDK/Data]; Data Architecture [Authority, Structure]; Infrastructure Architecture [System needs, data storage].
EA must apply Zero Trust to remove gateway (CISA provides maturity model and DoD framework).
DevSecOps software factory should be 1st (WO?) as everything is software defined.
At my company we have core software for software factory. I am a trusted technical advisor to military DIB and federal for efforts.
Discover and document current products languages they are written in ID if c onnected to network.
You have done some of this before. You have a foundation. What if the foundatin needs to change?
Open sourcing data products prod artifacts.
How will you protect IP and trade secrets within the EA?
EA diverse stake holder? Open source env everyone has easy access to, everyone can contribute to.
Get to the cloud internal hybrid.
EA influence: business architecture, governance, external; EA Systems: solution, data, infrastructure.
Make available content easy to find. Measure usability: effectiveness, efficiency.
What's first?Working groups for continuing education and professional development.
Build it around the data.
Start with GCIA and FACE since TNG and OPNS are joined.
If EA is service based then define the/a list of possible-note for each service performance.
Define how shared SVCS will be sustained who is responsible for evolution compatability etc.
Early talks and implementing of DoD's responsible AI initiatives.
Ownership/Service boundaries to reduce impacts of future change.
Identify what you want to know. What is your problem statement at each level: user, trainer, CMDR, Dep Army.
What's first? Determine app modernization strategy: 5 R's: Rehost, refactor, rearchitect, rebuild, replace.
Develop governance structure: align to existing entities, align to $, form community to establish standards, break into manageable groups.
Inventory of existing systems: Interfaces, business processes, data models.
How do we do open architecture in classified data?
Open, modular, low/no code platform.
Working groups: DevSecOps, data platform, AI/ML.
Understand interfaces, what is connected.
Data standards, K8S standards, digital twin standards.
Understand the data-survey users.
AI interconnectivity standards are critical early.
Build models of design as a start position.
Working group for AI (ML, cognitive AI, Hybrid AI).
Working groups: enterprise, interface, definition working group.
Our company reorganized to create an innovation factory.
How to transparently share data/code as needed across the enterprise (sharing methods such as cloud strategy).
Standardization is a stage of technology development, needs mature components. What are they? How do they relate?
Governmenthosted development env portal. US Army (i.e. DI2E).
Reference architecture in tool agnostic format.
Priorities: standards for data, data strategy.
Need to set expectations for who pays for what. Will PEO STRI pay for all EA tool licenses? Will EA work be part of one future contract or will it be part of all future contracts?
Common metadata standards.
Detailed roadmap to integration flexible standards as initial boundaries.
Important desired characteristics for EA: Standard comm layer which is light weight and fast, Common data structure and format.
Choosing a common open development formats ie. Container/CRI-0 CNCR Devs stds Unreal Eng or Unity.
Support stds from bottom up start w/ infrastructure then build on it.
DevSecOps: Diversity can be achieved through invitations to diversity groups to get representation.
Let industry free to work. How, care in govt over control.
Stakeholder partner vendor collaboration. "One team, one fight."
Collaboration.
Leadership alignment.
Industry incentive strategy: how to show $, positive delta to business model.
Integrated communication.
Feedback and comms.
Collaboration.
Involve all potential users/stakeholders (or at least a representative).
What's first: publish current progress and lessons learned on awarded programs tasked with developing common frameworks.
Determine the common unifying objective(s) for collaboration.
What's first: Continued collaboration and engagement with trusted advisers.
Acquisition strategy must drive collaboration not competition current process drives industry to compete.
Company established boards to review more performant technology.
Establish feedback loops at multiple points in EA cycle.
Understand data needs and use cases for all stakeholders/users.
To be available 24/7 for collaboration.
People.
Define data architecture, define business requirements.
Understand common requirements and leverage.
Common set of standards.
Early? Collaboration env (SDKS, Pipeline CI/CD); Agile: common increments schedule across projects.
What's first: collaborative environment to enable testing and development of standards/process/procedures.
Environment must be observable for metrics and agile/flexible for rapid iteration.
Consideration for what is first: 1. inventory of systems, data, infrasturcture; 2. align business processes; 3. overlap governance; 4. map interoperability.
ID the needs for sim interoperability.
Behaviors: equip our people to be transparent/vulnerable. Share what we don't know or do well.
Let the mission drive the tech and not the other way around.
Focus on a few key initiatives. Get something done. Do not focus on all of them.
Be mindful of multimedia content creation pipelines.
Published digital acquisition strategy and templates (i.e. model based proposals).
Understand the constraints: policy issues.
Understand and agree on scope.
People/process: Current state assessment, determine future state, gap analysis.
Early consideration: baseline the entire portfolio: In dev, offered, being retired.
What we did: establish center of excellence to assist teams gain early wins with new solution that they can build on.
EA-Get something out now but insure it gets better over time.
What's first: fully define the "so what" overall stakeholders (value); organization changes to drive EA;