|
Join the Joint Improvised Explosive Device Defeat
Organization (JIEDDO) Counter-IED Operations Intelligence Center (COIC)
Strategic and Enterprise Engineering Team on the just-awarded first-ever
Systems Engineering and Technical Assistance 5-year contract!
a. Bridge the gap
between evolving technology and practical implementation. Apply information and knowledge
engineering disciplines to develop and maintain a
JIEDDO-COIC enterprise architecture (EA), using the DOD
Architecture Framework (DODAF) for Operational and System Architecture
Design and Development. Maintain
the system Interfaces and the overall JIEDDO-COIC architecture in an
Architecture Design and Description Document (AD&DD) to document the
COIC baseline. Update the
AD&DD to describe major technology insertion changes including the
interface design description of systems, hardware configuration items,
computer software items, or other systems components. Apply DoD standards and architecture requirements to the
design of all networks, hardware, software and information system
processes.
b. Develop
systems engineering/enterprise engineering processes that identify user’s
needs, requirements, and constraints and then translate the user
requirements into new initiatives that meet DoD
architecture standards. Engage
with DoD users to identify the users' problems
and needs for information sharing and advanced collaboration for
JIEDDO-COIC. Analyze the users'
needs, requirements, and constraints.
Address interfaces, software accreditation, enterprise management,
and data standards in support of the DoD user.
c. Identify the
system requirements for the counter IED mission based on mission gaps and
mission needs, architecture enhancements, new software tools and new
technology. Capture these
requirements in a System Requirements Document (SRD). The SRD will specify the requirements
and the methods to be used to ensure that each requirement has been
met. Develop performance metrics
for each requirement and document them in a Measures of Effectiveness (MOEs) section as part of the SRD document.
d. Conduct
periodic System Requirements Reviews (SRRs) for
each new system or major technology insertion. Include an analysis of system
requirements. The objective of the
SRR is to ascertain the adequacy of the developer’s efforts in defining
system requirements.
e. Assist with
defining vendor-neutral operational and technical requirements,
structures, and architectures and crafting the plans for implementation.
f. Review all
Material Action Requests (MAR) to ensure that proposed material solutions
will conform to the EA, will employ Commercial Off The Shelf (COTS) items
or Non-Development Items (NDI) to the maximum extent, and include an
assessment of cost effective alternatives. Where COTS or NDI solutions are not
available, proven and mature technology should be identified and
reviewed.
g. Conduct a
System Design Review (SDR) that reflects each system or major technology
insertion to the COIC baseline when the system definition effort has
proceeded to the point where system characteristics are defined and the
configuration items are identified.. This review is conducted to evaluate
the optimization, correlation, completeness, performance metrics, and
risks associated with the allocated technical requirements. Document the reviewed system design in
a System Design Document (SDD).
h. Validate
compliance of systems architectures and functional baselines with the EA
|
