Sign In
  • Question

    Are there any documented best practices, policies or guidelines for implementation of the following roles within PD, PM, PEO or Acquisition Executive staff? Specifically Chief Architect, Chief Data Officer (CDO), Chief Design Officer, Chief Engineer (ChEng) / Chief System Engineer / Chief Engineering Officer, Chief Cyber-Security Officer (or Chief Information Security Officer), Chief Innovation Officer (CINO), Chief Integration Officer (CXO), Chief Intellectual Property Officer (CIPO), Chief Knowledge Officer (CKO), Chief Scientist or Chief Science Officer, Chief Technology Officer (CTO), Chief Information Officer (CIO), Chief Software Engineer (CSE), Chief Information Technology Engineer (CITE), Chief SATCOM Engineer, Chief Network Engineer, Chief Wireless Network RF Engineer, Thank you. P. Terzulli APG, MD


    Policy exists for roles and responsibilities for certain positions in DoD. These can be used as guidelines to be applied and tailored to fit the needs and circumstances of a particular organization.

    See Deputy Secretary of Defense memo, SUBJECT: Guidance Regarding Cyberspace Roles, Responsibilities, Functions, and Governance within the Department of Defense, 9 June 2014 for assignment of roles and responsibilities to the DoD CIO and Principal Cyber Advisor (PCA) as shown below. Also see DoDD 5144.02, DoD Chief Information Officer (DoD CIO), 21 November 2014 for a complete listing of the DoD CIO’s roles and responsibilities.

    Chief Information Officer:
    DoD CIO: Shall serve as the principal staff assistant and senior advisor to the Secretary of
    Defense on matters related to IT systems and architecture, information resource
    management (IRM) and efficiencies, and cybersecurity standards, in coordination with the
    PCA. In these capacities, the DoD CIO shall:
    • Develop policy guidance and prescribe standards for: network operations, the
    secure configuration and maintenance of IT systems, interoperability of DoD
    systems and interface between non-DoD systems, and enterprise-wide architecture
    • Conduct oversight and manage implementation of: an integrated IT architecture,
    compliance with IT network policies and technical standards, IT programs and
    systems performance, the development and maintenance of network contingency
    and crisis response communications plans, and the IT budget.
    • Provide policy guidance and advice on: IT network security, cybersecurity
    standards, IT networks and IRM budget requests, and IT infrastructure procurement
    and investment decisions. (DoDD 5144.02, paragraph 3, 14 Nov 2014). Specific duties are also listed in detail in this paragraph.

    Principal Cyber Advisor (PCA):
    Shall serve as the principal civilian advisor to the Secretary of Defense on offensive and defensive cyberspace operations and missions. The PCA shall advise the Secretary with respect to acquisitions related to cybersecurity and cyber offensive and defensive capabilities, but this advisory role shall not be construed to affect the authorities of the Under Secretary of Defense for Acquisition, Technology, and Logistics (USD (AT&L)) or of the Acquisition Executives of the Military Departments. In addition, nothing in this Memorandum shall be construed to mean that the PCA has operational responsibilities for cyber defensive or offensive missions. The PCA shall:
    • Serve as the principal advisor within the senior management of the Department
    (after the Secretary and Deputy Secretary) on military cyber forces and activities.
    • Develop and oversee the implementation of DoD cyber policy and ensure that DoD
    activities support national cyber strategies and policies.
    • Oversee Department-wide cyber training programs, activities, resources, personnel,
    operations, acquisitions (in consultation with the USD (AT&L)), and technology (in
    consultation with USD (AT&L) and DoD CIO).

    Lead Systems Engineer: Interim DoDI 5000.02, Enclosure 3
    • In general, the Lead Systems Engineer supports the PM in embedding systems engineering in program planning and execution to support the entire system life cycle through a systems engineering plan (SEP).
    • A SEP is required for each milestone review, beginning with Milestone A, and for the Development RFP Release Decision review prior to Milestone B.
    - The purpose of the SEP is to guide all technical aspects of the program. It should be established early in the Materiel Solution Analysis phase and updated continually.
    - A systems engineering plan (SEP) is a "living" document that captures a program's current and evolving systems engineering strategy and its relationship with the overall program management effort.
    - The SEP will describe the program’s overall technical approach, including key technical risks, processes, resources, organization, metrics, and design considerations. It also details the timing and criteria for the conduct of technical reviews.

    Chief Technology Officer (CTO) of DoD – Under Secretary of Defense (Research and Engineering)
    • Work to find ways to get emerging technologies from laboratories, the research and engineering side of their development, into the hands of the warfighters as rapidly as possible. Goal is for transitions to be on a scale of weeks and months, rather than years or decades.
    • “Classic” mission is to find and invest in emerging ideas that will be major innovations five to ten years down the road — the “game-changers” like today’s unmanned vehicles.
    • Reduce the cost, risk and timeline of defense system acquisition. They work with service program offices to make sure technologies are being acquired quickly and at the best price.
    • Finally, work with the White House and other government agencies to ensure there is a “strong technical workforce” in the future for the Department of Defense and the nation as a whole.

    As noted above, the definition of the roles and responsibilities for other positions is an organizational prerogative – some selected positions follow.
    Chief Technology Officer – General Business Definition
    A chief technology officer is a top corporate executive who makes decisions regarding the development and application of new technologies. He or she often oversees engineers and technical professionals in the research and design of new products and systems. In addition, the chief technology officer often becomes involved in marketing and accounting strategies that use information technology (IT) systems. He or she meets regularly with other executives to discuss the success of the business and determine ways to improve profits. In order to fulfill the vast responsibilities of a chief technology officer, an individual must have very strong leadership, communication, and problem solving skills.

    Chief Knowledge Officer (CKO) – General Business Definition
    A Chief Knowledge Officer (CKO) is a leading executive who is responsible for ensuring that an organization maximizes the value it obtains from one of its largest and most important resources - knowledge.

    What is Knowledge Management?

    • Installing and designing techniques and processes to protect, create, and exercise known knowledge.
    • Creating and designing environments and actions to release and discover knowledge that is not well-known or tacit knowledge.

    Open full Question Details