<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<?xml-stylesheet type="text/xsl" href="../part2stratml.xsl"?><PerformancePlanOrReport><Name>About MultiPlex.studio</Name><Description/><OtherInformation>AFWERX Multi-Domain Operations Challenge -- MultiPlex.studio led a team of Subject Matter Experts and partner firms Technica and Basil Security in developing a submission for the AFWERX MDO Challenge. We were selected for the AFWERX Fusion MDO Showcase, July 23rd-24th in Las Vegas.</OtherInformation><StrategicPlanCore><Organization><Name>MultiPlex.studio</Name><Acronym>MPS</Acronym><Identifier>_8e7e10fe-3a44-11eb-8420-18932883ea00</Identifier><Description>Multiplex.studio was formed to tackle the AFWERX MDO Challenge and is the partnership between several independents, Technica and Basil Security.</Description><Stakeholder StakeholderTypeType="Organization"><Name>Technica</Name><Description>Technica brings their SmartFog platform to the equation which will be used as the backbone of this proposal and ...</Description></Stakeholder><Stakeholder StakeholderTypeType="Organization"><Name>Basil Security</Name><Description>Basil Security’s Policy Enforcement Engine will be leveraged to distribute data according to a multi-level classification policy as well as acting as a broker for distributing encryption keys according to that policy.</Description></Stakeholder><Stakeholder StakeholderTypeType="Generic_Group"><Name>MultiPlex.studio Executive Team</Name><Description/></Stakeholder><Stakeholder StakeholderTypeType="Person"><Name>Jason Lind</Name><Description>Coalition</Description></Stakeholder><Stakeholder StakeholderTypeType="Person"><Name>Nick Chadwick</Name><Description>Ops</Description></Stakeholder><Stakeholder StakeholderTypeType="Person"><Name>Mitchell Maddox</Name><Description>Command</Description></Stakeholder></Organization><Vision><Description>Secure, resilient, real-time communications</Description><Identifier>_8e7e12ac-3a44-11eb-8420-18932883ea00</Identifier></Vision><Mission><Description>To tackle the AFWERX Multi-Domain Operations Challenge</Description><Identifier>_8e7e1392-3a44-11eb-8420-18932883ea00</Identifier></Mission><Value><Name/><Description/></Value><Goal><Name>R&amp;D</Name><Description>Perform research and development</Description><Identifier>_8e7e1478-3a44-11eb-8420-18932883ea00</Identifier><SequenceIndicator/><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>Formed to tackle the AFWERX Multi-Domain Operations Challenge we are now performing Independent Research and Development in the areas of Operational Risk Management and Secure, Resilient and Real-Time Communications.</OtherInformation><Objective><Name>Risk</Name><Description>Develop the use cases and architecture for Dynamic Operational Risk Assessment</Description><Identifier>_8e7e1554-3a44-11eb-8420-18932883ea00</Identifier><SequenceIndicator>1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>Dynamic Operational Risk Assessment -- This requirement began as SBIR AF192-057 "Dynamic, Risk-Based, Situational Awareness and Response" and while we attracted intense interest from several Subject Matter Experts we ultimately concluded that the SBIR mechanism did not provide enough funding for all our contributors and partners. We are now developing the use cases and architecture independently with the intention of identifying government and civilian customers to fund the development effort.</OtherInformation></Objective><Objective><Name>Communications</Name><Description>Develop the architecture for a blockchain authentication mechanism to achieve secure, resilient and real-time communications</Description><Identifier>_8e7e15d6-3a44-11eb-8420-18932883ea00</Identifier><SequenceIndicator>2</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name>Secure, Resilient &amp; Real-Time Communications Working Group</Name><Description/></Stakeholder><OtherInformation>During our analysis of the AFWERX project we discussed introducing blockchain as an authentication mechanism to achieve Secure, Resilient and Real-Time Communications however discovered the domain was not mature enough to include that in the proposal. We have started a working group to develop the architecture for such a product.</OtherInformation></Objective></Goal></StrategicPlanCore><AdministrativeInformation><StartDate/><EndDate/><PublicationDate>2020-12-09</PublicationDate><Source>http://multiplex.studio/</Source><Submitter><GivenName>Owen</GivenName><Surname>Ambur</Surname><PhoneNumber/><EmailAddress>Owen.Ambur@verizon.net</EmailAddress></Submitter></AdministrativeInformation></PerformancePlanOrReport>
