I deliberately several (a very tiny subset) of my job's acronyms in that post to show how cryptic the lingo becomes. Here's the translation:

Take my job - I'm working to create and integrate the OA for SSA with CCIC2S, SISP, SC2WS, OCS, DCS, and RAIDRS. I'm also supporting the SSA C2 COI DMWG by taking my OV-7 LDM work and helping convert it to SV-11 Physical Schema (as specified in the DoDAF) to support development of XML schema to enable NetCentric Operations. In overtime, I also work on integrating DMOS with CCIC2S.</I

Take my job - I'm working to create and integrate the Operational Architecture (OA) for Space Situation Awareness (SSA) with the Combatant Commander's Integrated Command and Control System (CCIC2S), Single Integrated Space Picture (SISP), Space Command and Control Weapon System (SC2WS), Offensive Counterspace (OCS), Defensive Counterspace (DCS), and the Rapid Attack Identification and Reporting System (RAIDRS). I'm also supporting the Space Situation Awareness Command and Control Community of Interest (SSA C2 COI) Data Management Working Group (DMWG) by taking my Operational View-7 Logical Data Model (OV-7 LDM) work and helping convert it to System View-11 (SV-11) Physical Schema (as specified by the Department of Defense Architecture Framework (DoDAF) to support development of eXtensible Markup Language (XML) schema to enable NetCentric Operations. In overtime, I also work on integrating Distributed Mission Operation System (DMOS) with CCIC2S (already defined).

WHEW! Like I said, space is an acronym rich environment. We once tried to assemble a glossary of terms used for military satellite operations. It quickly collapsed under its own weight. Just one satellite program - the DSCS (Defense Satellite Communications System)-III that I worked on had over 1000 telemetry acronyms and perhaps a couple thousand more used in the program. There simply wasn't enough time or resources to assemble the glossary.