Chief Engineer Lead Architect

Integral•Fort Meade, MD

64d

About The Position

The Chief Engineer Lead Architect will leverage the strategic use of data rights to meet both short and long-term program goals and ensure an exit strategy that enables a level competitive playing field for the DISA Global Force Management (GFM) Program Management Office (PMO) that supports system availability, stability, and interoperability of JPES and JCRM. Identify alternative solutions and sources across the entire life cycle of the solution; Insert new or additional technology; Transition to another contractor - potentially with another platform solution; Through a competitive process; or through an appropriate Exit Strategy. Explain the use of and define its process for identifying and justifying proprietary, vendor- unique, open sourced or closed interfaces, code Modules, hardware, firmware, or software to be used. When interfaces, hardware, firmware, or Modules that are proprietary or vendor-unique are required, demonstrate those proprietary elements do not preclude or hinder other component or Module developers from interfacing with or otherwise developing, replacing, or upgrading open parts of the system. Develop Government Purpose Rights (GPR) for data (all types) including development information (e.g., backlog items, user stories, requirements, business processes, business rules, workflows, business logic, and configuration items in a manner that they can be easily read, parsed through, and re-used by another platform solution) and operational information (e.g., archived case information, active case information, lookup data, etc.) and including source code - for all custom developed interfaces and components. Develop the architecture to provide for insertion of COTS into the system and demonstrate that COTS, Reusable Non-Developmental Item (NDI), and other components are supported logistically throughout the life cycle. Describe and demonstrate the strategy for reducing product or system and associated supportability costs through insertion of COTS and other reusable COTS or NDI products. Establish a process to logistically support COTS or NDI products. Describe the availability of commercial support services required for life cycle support and demonstrate they are adequate to ensure long-term support for COTS or NDI products. Provide the proposed methodology for pass through of COTS warranties to the Government. Provide a list to the Government of all proprietary, vendor-unique, open source, closed interfaces, code Modules, hardware, firmware, software (including COTS), all other components and technical and other data and their associated data rights and intellectual property assertions that will be used in performing this effort.

Requirements

BA/BS degree in an Engineering discipline. An additional four years of experience in lieu of a degree is acceptable.
At least 10 years of experience in software development
Secret Clearance

Responsibilities

Identify alternative solutions and sources across the entire life cycle of the solution
Insert new or additional technology
Transition to another contractor - potentially with another platform solution
Explain the use of and define its process for identifying and justifying proprietary, vendor- unique, open sourced or closed interfaces, code Modules, hardware, firmware, or software to be used.
When interfaces, hardware, firmware, or Modules that are proprietary or vendor-unique are required, demonstrate those proprietary elements do not preclude or hinder other component or Module developers from interfacing with or otherwise developing, replacing, or upgrading open parts of the system.
Develop Government Purpose Rights (GPR) for data (all types) including development information (e.g., backlog items, user stories, requirements, business processes, business rules, workflows, business logic, and configuration items in a manner that they can be easily read, parsed through, and re-used by another platform solution) and operational information (e.g., archived case information, active case information, lookup data, etc.) and including source code - for all custom developed interfaces and components.
Develop the architecture to provide for insertion of COTS into the system and demonstrate that COTS, Reusable Non-Developmental Item (NDI), and other components are supported logistically throughout the life cycle.
Describe and demonstrate the strategy for reducing product or system and associated supportability costs through insertion of COTS and other reusable COTS or NDI products.
Establish a process to logistically support COTS or NDI products.
Describe the availability of commercial support services required for life cycle support and demonstrate they are adequate to ensure long-term support for COTS or NDI products.
Provide the proposed methodology for pass through of COTS warranties to the Government.
Provide a list to the Government of all proprietary, vendor-unique, open source, closed interfaces, code Modules, hardware, firmware, software (including COTS), all other components and technical and other data and their associated data rights and intellectual property assertions that will be used in performing this effort.