The Essence of MITRE Systems Engineering
The section The Evolution of Systems Engineering notes that the systems engineering discipline is defined by the context or environment in which it is embedded. This companion section describes more specifically how the distinctive attributes of MITRE systems engineering are shaped by the expectations of our sponsors and customers and further formed by our corporate interpretation of the quality systems engineering required to meet those expectations.
Sponsor Expectations for MITRE Systems Engineering
The U.S. Federal Acquisition Regulation (FAR) part 35.017 sets forth federal policy on the establishment and use of Federally Funded Research and Development Centers (FFRDCs) and related sponsoring agreements [1]. A portion is excerpted below.
35.017 Federally Funded Research and Development Centers.
(a) Policy.
...
...
(2) An FFRDC meets some special long-term research or development need which cannot be met as effectively by existing in-house or contractor resources. FFRDC's enable agencies to use private sector resources to accomplish tasks that are integral to the mission and operation of the sponsoring agency. An FFRDC, in order to discharge its responsibilities to the sponsoring agency, has access, beyond that which is common to the normal contractual relationship, to Government and supplier data, including sensitive and proprietary data, and to employees and installations equipment and real property. The FFRDC is required to conduct its business in a manner befitting its special relationship with the Government, to operate in the public interest with objectivity and independence, to be free from organizational conflicts of interest, and to have full disclosure of its affairs to the sponsoring agency. It is not the Government's intent that an FFRDC use its privileged information or access to installations equipment and real property to compete with the private sector.
...
...
(4) Long-term relationships between the Government and FFRDC's are encouraged in order to provide the continuity that will attract high-quality personnel to the FFRDC. This relationship should be of a type to encourage the FFRDC to maintain currency in its field(s) of expertise, maintain its objectivity and independence, preserve its familiarity with the needs of its sponsor(s), and provide a quick response capability.
Some phrases from this excerpt stand out as particularly important factors that influence the way in which MITRE executes its systems engineering roles and responsibilities:
- Meets some special long-term research or development need which cannot be met [otherwise]
- Private sector resources
- Access, beyond that which is common to the normal contractual relationship
- Operate in the public interest with objectivity and independence
- Free from organizational conflicts of interest
- Full disclosure of its affairs to the sponsoring agency
- Not...compete with the private sector
- Currency in its field(s) of expertise
- Familiarity with the needs of its sponsor(s)
MITRE's individual FFRDC sponsoring agreements further shape how we perceive and practice systems engineering [2, 3, 4, and 5]. The FFRDC sponsoring agreements for the C3I [Command, Control, Communications, and Intelligence], CAASD [Center for Advanced Aviation System Development], CEM [Center for Enterprise Modernization], and SEDI [Homeland Security Systems Engineering and Development Institute] further delineate the purpose and role of each FFRDC, its core work, relationship to the sponsoring organization, and other details of its operation. Despite obvious differences among the sponsoring agreements, two consistent themes are evident: Each FFRDC is expected to be doing appropriate work that answers the nation's needs, and that work needs to be done well. Within MITRE, we sometimes use the shorthand "do the right work" when referring to the former and "do the work right" when referring to the latter. These two fundamental characteristics of quality systems engineering are understood and practiced by MITRE. Below are excerpts from each of the four sponsoring agreements that illustrate these aspects of MITRE systems engineering.
Do the Right Work
- The work performed...will...be...of both long-term and immediate homeland security concern... [SEDI]
- Identification of critical capability gap[s]...particularly in areas where technology...contribute[s] substantially to solutions. [SEDI]
- Subjects integral to the mission and operations of the sponsoring offices. [SEDI]
- Provid[e] technical and integration expertise...particularly in the evolution of the most complex and critical homeland security programs. [SEDI]
- Promote compatibilities across the various homeland security platforms and equipment...through...improved interoperability and information sharing within the homeland security enterprise. [SEDI]
- Work on the most complex homeland security systems that will evolve capabilities... [SEDI]
- Help the Department develop a DHS system of systems approach... [SEDI]
- Address the long- and short-term evolutionary change necessary to modernize the NAS. [CAASD]
- Development and evaluation of plans for the evolution and integration of ATM system capabilities. [CAASD]
- Problems that do not stand alone but are so linked to others that highly specific analysis may be misleading. [CAASD]
- Issues that cannot be formulated sharply enough in advance. [CAASD]
- Unprecedented problems that require unique research methods. [CAASD]
- Perform studies, analysis and concept formulation for continued...modernization and development of the NAS. [CAASD]
- Works with DoD [Department of Defense] to research, develop, integrate, field, sustain and modernize timely, affordable and interoperable C4ISR [Command, Control, Communications, Computers, Intelligence, Surveillance, and Reconnaissance] solutions, systems and technology. [C3I]
- Provid[e] enterprise systems engineering and integration support throughout the C4ISR mission area. [C3I]
- Help identify, define, and recommend solutions to problems as a trusted partner of the Sponsors' management team. [CEM]
- Focus...on core work that promotes C4ISR integration/interoperability. [C3I]
- [Maintains] an end-to-end understanding of the C4ISR mission area with emphasis on enterprise architectures that enable increasingly advanced and more fully integrated systems of systems, system acquisition (including technical support to source selection), integration of commercial and military technologies and interoperability.[C3I]
Do the Work Right
- Produces high-quality work of value to the sponsors [SEDI]
- ...performance of objective, high-quality work... [SEDI]
- Provide the government with the necessary expertise to provide best lifecycle value... [SEDI]
- Develop and promote standardization of effective and efficient system engineering best practices... [SEDI]
- The work performed...will...be authoritative…[SEDI]
- ...purpose is to provide special technical expertise [SEDI]
- Simultaneously direct...efforts to the support of individual programs and projects for enterprise modernization, assuring that these individual programs and projects operate effectively with one another and efficiently support the business objectives of the Government. [CEM]
- Provide exceptional technical competence in support of the Sponsors' design and pursuit of mission goals. [CEM]
- Partner with the Sponsors in pursuit of excellence in public service. [CEM]
- Maintain a commitment to technical excellence...in everything it does. [CEM]
- Promotion of technical excellence...will be paramount. [CAASD]
- ...shall be responsible to the FAA with regard to the progress and quality of...NAS development efforts undertaken by it. [CAASD]
- ...staff...encouraged to publish...in professional journals...to have the quality of such work subject to peer scrutiny. [CAASD]
- maintaining objectivity and high technical quality. [C3I]
- ...maximize value... [C3I]
- ...while serving the immediate needs of the many individual programs it supports, the C3I FFRDC aligns its work program to assist in achieving integrated enterprise capabilities... [C3I]
- ...information as an enterprise asset to be shared... [C3I]
MITRE Expectations for Quality in Systems Engineering [6]
Quality in MITRE's systems engineering includes aspects of both delivering an inherently good product or service and meeting external expectations. For MITRE, external expectations are set by multiple stake-holders, including not only our immediate customers but also the end users of the capabilities we help create, our FFRDC sponsors (and those above them who set expectations for FFRDCs more generally), and our Board of Trustees (who are external to day-to-day company affairs).
For the most part, the higher-level expectations from our sponsors and Board align with each other and with our internal aspirations for "good" as embodied by our strategic framework. They also align with how MITRE can and should uniquely contribute to meeting end user needs. These alignment points include:
- Working in the public interest on issues of critical national importance by...
- Proactively applying systems engineering and advanced technology to bring...
- Timely and innovative/creative solutions to key, hard problems, balancing...
- Technical feasibility with economic and political practicality, and leveraging...
- Breadth and depth of engineering with mission/business domain knowledge, while...
- Providing an integrating perspective across boundaries, and always...
- Retaining objectivity and being cost effective in our work.
To meet these expectations we need to be doing appropriate work that answers the nation's needs, and we need to do it well. This is the key requirement that cuts across our four sponsoring agreements. We also need to satisfy our immediate customers. And we need to invest in developing quality relationships with decision-makers, stakeholders, and our customers, to shape our work and present results so that they have the impact they deserve. Meeting our customers' expectations requires that we provide value in the quality of our contributions.
Therefore, quality in MITRE systems engineering can be defined as:
- Degree to which results of systems engineering meet the higher-level expectations for our FFRDCs—resulting in usability and value for end recipients
- Degree to which results of systems engineering meet expectations of our immediate customers—service and performance.
The pressures on our customers often lead them to ask for quick reaction responses from MITRE. To the extent that a quick response is practical, we must provide it. (When the imposed constraints make an informed response impractical, we need to define the extent to which we can make an informed response, explain why we cannot go further, and refuse the remainder of the task.) And our processes for identifying and leveraging applicable past analyses and data, informed professional judgments, and relevant experiences (either within or external to MITRE) need to be focused on enabling the highest quality response within the constraints imposed. Whenever possible we should document our delivery (even after the fact)—the assumptions made, the methods used, and the results conveyed. We also must develop our knowledge base to continually improve our ability to respond to future requests related to our core competencies.
Moreover, we must assess the risks of quick responses to understand the possible issues with their accuracy and completeness, including the potential consequences of these issues—and so inform the customer. When the risk is high, we should strongly recommend a plan for a more complete, fact-based analysis, utilizing, as needed, trade-space exploration, modeling and simulation, experimentation, proof-of-concept prototyping, etc. Clearly, circumstances requiring in-depth study, especially if associated with key national capability outcomes, demand the highest quality work. This entails careful planning and work shaping, appropriate staffing and resources, peer and management consultation and review throughout the execution of the work, and socializing and delivering the results so that they are correctly interpreted and acted upon. Importantly, the higher-level expectations on MITRE can only be met when a significant fraction of our work goes beyond quick response activities, so finding ourselves in these circumstances should be relatively common.
The higher-level expectations on MITRE push us beyond responding to customer requests toward proactively identifying key issues on which we can make a difference. These often involve enterprise objectives such as integration and interoperability for information sharing across the government (and, at times, beyond), which may exceed the bounds of an individual customer's purview. When these proactive initiatives lead to substantive efforts, they also demand the highest quality work, with all the same attributes discussed above applied to their planning, execution, and delivery.
In summary, MITRE needs to provide its customers with "quick and dirty" products when necessary, making them as "clean" as possible but conveying a clean/dirty assessment along with the product. Higher-level expectations for MITRE's FFRDC contributions require us to often work more substantively, with an even greater emphasis on quality for our work. Quality, then, involves both doing enough of the right work, and doing all of our work (but especially the higher impact work) right. It also includes building relationships so that high impact is, in fact, realized. These objectives are reachable only if we all understand the expectations, are frank and open about assessing the work we're asked to do, foster a culture that values quality and learns from both mistakes and successes, follow through (internally and with our customers) on resource allocations, and pay attention to important relationships. Upper management needs to take the lead, but we all need to contribute. Especially with the immediate customer, it's often the project staff that have the frequent connections that influence the customer's perception of our quality and the acceptance of our recommendations.
The Successful MITRE Systems Engineer
What does successful systems engineering look like at MITRE? What is the secret formula for it? As noted early in the companion section to this one—The Evolution of Systems Engineering—there is no single definition of systems engineering and so there is no single definition of success. Much depends on the context in which the systems engineering is being practiced. Nevertheless, there are high-level criteria that strongly correlate with successful MITRE systems engineers. These are summarized below. They are excerpted from the MITRE Systems Engineering Competency Model [7].
For more information on the Systems Engineering Guide, or to suggest an article, please contact us.
Criteria for Successful MITRE Systems Engineers |
Successful MITRE Systems Engineers:
- Define the sponsor's and customer's problem or opportunity from a comprehensive, integrated perspective.
- Apply systems thinking to create strategies, anticipate problems, and provide short- and long-term solutions.
- Adapt to change and uncertainty in the project and program environment, and assist the sponsor, customer, and other stakeholders in adapting to these.
- Propose a comprehensive, integrated solution or approach that:
- Contributes to achieving the sponsor's, customer's and other stakeholders' strategic mission objectives in a changing environment,
- Can be feasibly implemented within the sponsor's and customer's political, organizational, operational, economic and technical context,
- Addresses interoperability and integration challenges across organizations, and
- Shapes enterprise evolution through innovation.
- Cultivate partnerships with our sponsors and customers to work in the public interest.
- Bring their own and others' expertise to provide sound, objective evidence and advice that influences the decisions of our sponsors, customers, and other stakeholders.
|
References & Resources:
- Office of Management and Budget, November 13, 2009, Federal Acquisition Regulation (FAR), 35.017.
November 21, 2008, DoD Sponsoring Agreement with The MITRE Corporation to Operate the C3I FFRDC.
September 25, 2005, Sponsoring Agreement between the FAA and The MITRE Corporation for the Operation of the CAASD FFRDC.
February 7, 2008, Sponsoring Agreement Among the IRS and Department of Veterans Affairs and The MITRE Corporation Operating the FFRDC formally known as the Center for Enterprise Modernization.
March 3, 2009, Sponsoring Agreement between DHS and The MITRE Corporation to Operate the Homeland Security System Engineering and Development Institute FFRDC.
MITRE, May 2008, Systems Engineering Quality at MITRE.
- MITRE, September 2007, MITRE Systems Engineering Competency Model, version 1.
|