Systems Engineer III:  Location: Columbia, MD   TS/SCI WITH FULL SCOPE POLYGRAPH REQ

Description:

Analyzes user’s requirements, concept of operations documents, and high level system architectures to develop system requirements specifications. Analyzes system requirements and leads design and development activities. Guides users in formulating requirements, advises alternative approaches, and conducts feasibility studies. Provides technical leadership for the integration of requirements, design, and technology. Incorporates new plans, designs and systems into ongoing operations. Develops technical documentation. Develops system Architecture and system design documentation. Guides system development and implementation planning through assessment or preparation of system engineering management plans and system integration and test plans. Interacts with the Government regarding Systems Engineering technical considerations and for associated problems, issues or conflicts. Ultimate responsibility for the technical integrity of work performed and deliverables associated with the Systems Engineering area of responsibility. Communicates with other program personnel, government overseers, and senior executives.

Qualifications:

• TS/SCI with current Full Scope Polygraph
• IAT Level II
• Late Shift Until 6pm (at least once a week) required
• Twenty (20) years experience as a SE in programs and contracts of similar scope, type and complexity is required.
• Five (5) years of additional SE experience may be substituted for a bachelor’s degree
• Demonstrated experience in planning and leading Systems Engineering efforts is required.
• Bachelor’s degree in System Engineering, Computer Science, Information Systems, Engineering Science, Engineering Management, or related discipline from an accredited college or university is required.
• Netapps experience a must.
• Help desk environment. At least one late shift required starting at 6pm. Patch days will require resources to assist later in the evening and flexing time during the week or EWW

Responsibilities:

• Netapps experience a must!
• Senior Linux Engineer and Netapp SME. Must understand how to configure Must have experience with NetApp data storage
• Help desk environment. At least one late shift required starting at 6pm. Patch days will require resources to assist later in the evening and flexing time during the week or EWW
• Manage system requirements and derived requirements to ensure the delivery of production systems that are compatible with the defined system architecture(s) – Department of Defense Architecture Framework (DoDAF), Service-oriented Architecture (SOA), etc
• Contribute to the development of sections of systems engineering documentation such as System Engineering Plans, Initial Capabilities Documents, Requirements specifications, and Interface Control Documents
• Assist with the development of system requirements, functional requirements, and allocation of the same to individual hardware, software, facility, and personnel components
• Coordinate the resolution of action items from Configuration Control Board (CCB) meetings, design reviews, program reviews, and test reviews that require cross-discipline coordination
• Participate in an Integrated Product Team to design new capabilities based upon evaluation of all necessary development and operational considerations
• Allocate real-time process budgets and error budgets to systems and subsystem components (U) Generate alternative system concepts, physical architectures, and design solutions
• Define the methods, processes, and evaluation criteria by which the systems, subsystems and work products are verified against their requirements in a written plan
• Develop system design solution that satisfies the system requirements and fulfills the functional analysis
• Review and provide input to program and contract work breakdown structure (WBS), work packages and the integrated master plan (IMP)
• Participate in the development of system engineering documentation, such as System Engineering Plans, Initial Capabilities Documents, Requirements Specifications, and Interface Control Documents
• Participate in interface definition, design, and changes to the configuration between affected groups and individuals throughout the life cycle
• Derive from the system requirements an understanding of stakeholder needs, functions that may be logically inferred and implied as essential to system effectiveness
• Derive lower-level requirements from higher-level allocated requirements that describe in detail the functions that a system component must fulfill, and ensure these requirements are complete, correct, unique, unambiguous, realizable, and verifiable
• Participate in establishing and gaining approval of the definition of a system or component under development (requirements, designs, interfaces, test procedures, etc.) that provides a common reference point for hardware and software developers
• Develop derived requirements for Information Assurance Services (Confidentiality, Integrity, Non repudiation, and Availability); Basic Information Assurance Mechanisms (e.g., Identification, Authentication, Access Control, Accountability); and Security Mechanism Technology (Passwords, cryptography, discretionary access control, mandatory access control, hashing, key management, etc.)
• Implement comprehensive SOA solutions
• Implement operational view, technical standards view, and system and services view for architectures using applicable DoDAF standards
• Review and/or approve system engineering documentation to ensure that processes and specifications meet system needs and are accurate, comprehensive, and complete
• Capture all interface designs in a common interface control format, and store interface data in a commonly accessible repository
• Assess each risk to the program and determine the probability of occurrence and quantified consequence of failure in accordance with an approved risk management plan
• In conjunction with system stakeholders, plan the verification efforts of new and unproven designs early in the development life cycle to ensure compliance with established requirements
• Prepare time-line analysis diagrams illustrating the flow of time-dependent functions
• Establish a process to formally and proactively control and manage changes to requirements, consider impacts prior to commitment to change, gain stakeholder buy-in, eliminate ambiguity, ensure traceability to source requirements, and track and settle open actions
• Manage and ensure the technical integrity of the system baseline over time, continually updating it as various changes are imposed on the system during the lifecycle from development through deployment and operations & maintenance
• Support the planning and test analysis of the DoD Certification/Accreditation Process (as well as other Government Certification and Accreditation (C&A) processes)
• Support the development and review of Joint Capability Integration Development System (JCIDS) documents (i.e., Initial Capability Document, Capabilities Description Document, IA Strategy)
• Provide technical direction for the development, engineering, interfacing, integration, and testing of specific components of complex hardware/software systems to include requirements elicitation, analysis and functional allocation, conducting systems requirements reviews, developing concepts of operation and interface standards, developing system architectures, and performing technical/non-technical assessment and management as well as end-to-end flow analysis
• Develop scenarios (threads) and an Operational Concept that describes the interactions between the system, the user, and the environment, that satisfies operational, support, maintenance, and disposal needs
• Conduct quantitative analysis in non-functional system performance areas like Reliability, Maintainability, Vulnerability, Survivability, Produceability, etc.) (U) Establish and follow a formal procedure for coordinating system integration activities among multiple teams, ensuring complete coverage of all interfaces
• Develop comprehensive SOA solutions
• Develop operational view, technical standards view, and system and services view for architectures using applicable DoDAF standards
• Conduct and/or approve end-to-end system trade analyses to optimize system operations over its life-cycle through the proper balance of non-functional system performance areas
• Use validated models, simulations, and prototyping to mitigate risk and reduce cost of system development (U) Ensure effective, periodic review and control of the evolving configuration of a system, both hardware and software components and associated documentation, during the life of the system
• Serve as a member of the CCB
• Develop system design alternatives that consider life cycle cost, reuse, complexity, risk, system expansion, and growth
• Develop alternative courses of action, workarounds, and fall-back positions with a recommended course of action for each risk, and monitor and re-evaluate risks at appropriate milestones. Monitors risks using earned value management (EVM) data
• Maintain knowledge of current and evolving agency, national, and international standards applicable to the system development of interest. Apply and enforce use of suitable standards to ensure consistency and interoperability of developer hardware and software
• As a participant within an Analysis of Alternatives (AoA) effort, recommend a preferred solution based on selection criteria adjusted for reasonableness and validity of assumptions, technology limitations, environmental impact, and life-cycle costs
• Provide technical direction for the development, engineering, interfacing, integration, and testing of all components of complex hardware/software systems to include requirements elicitation, analysis and functional allocation, conducting systems requirements reviews, developing concepts of operation and interface standards, developing system architectures, and performing technical/non-technical assessment and management as well as end-to-end flow analysis
• Improve standard integration strategies based upon rationale for previous decisions that resulted in improved integration performance
• Fully define interfaces in terms of origination, destination, stimulus, and data characteristics for software; and electrical and mechanical characteristics for hardware