• Review POA&M
• Final Draft of CSRs
• Stakeholder desired outcomes, requirements, etc.
‒ Expectation management…
• ESR edits and discussion
• Course changes, additions, deletions
• Quota
2

ACTION
√ • Website with working documents
√ • Schedule VTCs/TELECONs
√ • Survey from Space Cadre Advisor (draft from Suede by 1/6)
√ • Schedule In and Out Briefs with flags and others
√
√
• Inform protocol of flag visits and coordinate billeting and parking
• Coordinate lab tours and select student/faculty research briefs
√
√
√
√
√
• Action plans for each working group meeting
– Review last review outcomes and open items
– Review CSRs and ESRs (ABET objectives & outcomes)
– Data required for briefs (stats/billets/grads, quotas, etc.)
– AQD/PQS credit for SSO Certificate?
– Review Survey data
– Action plan for specific goals and outcomes
– Build briefs
– Draft N15 Curric Review letter and enclosures
• Pre-brief sponsors on results/gather any issues and build briefs
• Conduct necessary pre-briefs with GSEAS deans and mez
• Complete curricula review preps and draft N15 Curric Review letter
• Pre-brief NPS President/Provost/Associate Provost, final changes
• Review: Week of 24 February
– In-brief, tours, faculty meetings, student lunch, Out-brief
DEADLINE
12/30
1/7
1/10
1/10
1/10
1/10
1/7-13
1/7-17
1/7-2/7
1/30 week of 1/27
1/10 week of 2/3 week of 2/10
2/3-6
2/3-7
2/7-10
?
MASs
?
?
?
Suede
Suede
Suede
Suede
Suede
2/10-14 Suede week of 2/24 all
AO
Suede
Suede
Owens
Suede
Suede
Suede

• Core Skills Requirements include text description of skills as well as appropriate billet subspecialty coding basis
• Please review respective curriculum review letters, enclosure 3, for details on billet base and community manager approvals
‒ I need assistance in contacting Community
Managers and verifying their agreement to allow billets to be coded for 6206 sub spec code
• See notes for format
• Update CM names and approval dates
5

• Need confirmation of the following:
‒ Sponsor and Subject Matter Experts:
• Sponsor: VADM Ted N. Branch, Deputy Chief of Naval Operations for Information
Dominance (OPNAV N2/N6)
• Subject Matter Expert: CAPT Patrick Owens,
N2N6, Space Cadre Advisor, patrick.owens@navy.mil
6

• The Space Systems subspecialty code (6206) is achieved through an 18-month curriculum, including any required refresher training, intended to provide a command with an officer who can plan and manage the operation, tasking and employment of space surveillance, intelligence collection, communications, navigation and atmospheric/oceanographic/ environmental sensing systems.
• The following is a representative sample of requirements for which this subspecialty applies:
‒ On following 2 slides…
7

1. Space System Processes: Officers will be able to formulate operational requirements, plans, policies, architectures, operational concepts, doctrine and tactics for development and employment of space systems and the tasking, collection, processing, evaluation, and dissemination information products derived from spacebased systems.
2. Space System Capabilities and Design: Officers will have knowledge of the space environment, spacecraft design and operation, space systems technologies.
3. Orbital Mechanics and Analysis: Officers will have knowledge of orbital mechanics, systems analysis and integration, as well as information and knowledge management.
8

4. Space Liaison: Officers will perform liaison with other services, agencies, and/or industry concerning policy and procedures for operational employment of space systems and their information products.
5. Space Systems Assessment: Officers will perform operational evaluation of space systems performance.
6. Decision Superiority: Officers will provide recommendations to senior decision-makers regarding space systems operations, including the benefit of added space-based capabilities and the impact to operations if current space-based systems capabilities are denied to the force.
9

• Open for discussion for the purpose of laying out high level expectations that may lead to detailed discussion points, ESR edits and perhaps curriculum changes
‒ Outcomes will need to be expressed in terms of requirements (e.g. ESRs) and obtain concurrence of MAS and NPS
10

• Review Excel document for specific ESR wording
‒ “366&591 ESR Map 24JAN14.xlxs”
• Any required changes at this time?
‒ e.g. JP 3-14 edits, desired outcomes, etc.
11

• Any feedback for specific course or overall curriculum changes?
‒ Discussion which will loop back to ESRs…
12

• 6206P:
• 5500P:
Designat or
Total
1110
1120
2012
10
1
1
2013
1300 1
1810
1820
1 • 5500P:
3
0
1
2
1830 3 0
10
6
1
2014
0
0
0
6
2
2
2
2015
DRAFT
7
4
0
0
1
2
0
Designat or
Total
1120
1300
1400
1510
1810
1820
2012
1
3
3
10
1
1
1
2013
0
4
1
6
0
0
1
2014
2
3
1
9
1
0
2
2015
DRAFT
9
1
2
3
1
0
2
13

14

15

16

14
12
10
8
6
4
2
0
1 1 1 1
6206P/Q Coded Billets
1 1 1 1 1
3
1 1
13
5
2
6206P
6206Q

18

5500P/Q Coded Billets
25
20
15
10
35
30
5
0
1 1 1 1
3 3
2
33
4
1
2
1 1 1
5500P
5500Q

Break for SSE…

• Core Skills Requirements include text description of skills as well as appropriate billet subspecialty coding basis
• Please review respective curriculum review letters, enclosure 3, for details on billet base and community manager approvals
‒ I need assistance in contacting Community
Managers and verifying their agreement to allow billets to be coded for 5500 sub spec code
• See notes for format
• Update CM names and approval dates
27

• Need confirmation of the following:
‒ Sponsor and Subject Matter Experts:
• Sponsor: VADM William H. Hilarides, Naval
Sea Systems Command
• Subject Matter Expert: RDML James
Rodman, Jr., SPAWAR Space Field Activity with a shift to RDML Christian Becker, PEO
Space Systems/C4I
28

• The Space Systems Engineering subspecialty code (5500) is intended to provide a command with an officer who has the technical knowledge to plan and manage the research, design, development, acquisition, integration, testing, operation, tasking and employment of space surveillance, communications, navigation and atmospheric/oceanographic/ environmental sensing systems throughout their lifecycle.
• The following is a representative sample of requirements for which this subspecialty applies:
‒ On following 2 slides…
29

1. Formulate operational and technical requirements, system-level architectures, operational concepts, conceptual spacecraft designs and integration and test plans for development and employment of space systems and their information products, or the distribution, correlation and analysis of their information products .
2. Demonstrate technical knowledge of orbital mechanics and the space environment, remote sensing and payload design and spacecraft subsystems including communications, command and data handling, guidance and control, structures, propulsion, thermal control and electrical power .
30

3. Lead system of systems engineering efforts and direct design, development, acquisition, integration and testing of spacecraft and associated ground systems throughout their life-cycles including launch and on-orbit operations .
4. Perform liaison with other services, agencies, and/or industry concerning policy and procedures for requirements development and analysis for the design, acquisition and operational employment of national security space systems, ground support segments and their information products.
5. Perform technical evaluation of space systems design and performance and provide recommendations to senior decision-makers regarding space systems engineering issues .
31

• Open for discussion for the purpose of laying out high level expectations that may lead to detailed discussion points, ESR edits and perhaps curriculum changes
‒ Outcomes will need to be expressed in terms of requirements (e.g. ESRs) and obtain concurrence of MAS and NPS
32

• Review Excel document for specific ESR wording
‒ “366&591 ESR Map 24JAN14.xlxs”
• Any required changes at this time?
‒ e.g. JP 3-14 edits, desired outcomes, etc.
33

• Any feedback for specific course or overall curriculum changes?
‒ Discussion which will loop back to ESRs…
34