AT21IndustryDaySlideShow31Oct2006.ppt
PPT presentation 5 MB Posted
- Attached to
- Agile Transportation for the 21st Century (AT21)
- Solicitation number
- HTC711-07-R-0001
About this file
Briefing Slides for 10/31/06 Conference
View the file
Other files
Show all 48
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
| Opening Remarks | MG William Johnson, TCCS | ||
| Team Introductions | Mr. Dean Peebels, TCAQ | ||
| Program Overview | Mr. Dean Peebels, TCAQ | ||
| Requirements Briefing | Col(S) Jackie Van Ovost, TCJ3-O | ||
| 15 min Break | |||
| Performance Work Statement | Ms. Roni McDaniels, TCAQ | ||
| Request for Proposal | Ms. Lisa Gross, TCAQ | ||
| Small Business Participation | Ms. Michelle Mendez, TCAQ | ||
| Questions / Closing Remarks | Mr. Dean Peebels, TCAQ |
AT21 INDUSTRY DAY AGENDA
| Opening Remarks | MG William Johnson, TCCS | |
| Team Introductions | Mr. Dean Peebels, TCAQ | |
| Program Overview | Mr. Dean Peebels, TCAQ | |
| Requirements Briefing | Col(S) Jackie Van Ovost, TCJ3-O | |
| 15 min Break | ||
| Performance Work Statement | Ms. Roni McDaniels, TCAQ | |
| Request for Proposal | Ms. Lisa Gross, TCAQ | |
| Small Business Participation | Ms. Michelle Mendez, TCAQ | |
| Questions / Closing Remarks | Mr. Dean Peebels, TCAQ |
| Program Manager | Mr. Dean Peebels, TCAQ |
| Deputy Program Manager | Ms. Roni McDaniels, TCAQ |
| Functional Manager | LTC Darrell Gregg, TCJ3-I |
| Technical Manager | CDR Joel Price, TCJ6-PC |
| System Engineer | Mr. John Daum, MITRE |
| Supply Chain Advisor | Mr. Stu Draper, MITRE |
| Small Business Specialist | Ms. Michelle Mendez, TCAQ |
| Contracting Officer | Ms. Lisa Gross, TCAQ |
| Contracting Team | Ms. Terri Francoeur, TCAQ |
| Mr. Michael Pardue, TCAQ |
| TCJ3 Functional Team | Col(S) Jackie Van Ovost (Team Lead) |
| Lt Col Mark McLean | |
| CDR Matt Martin | |
| Lt Col Cliff Puckett | |
| LTC David Banian | |
| LTC Jeff Whelchel | |
| MAJ John Kaylor |
AT21 TEAM INTRODUCTIONS
Also introduce Mr. Jamison, J3-P, and Lori Farnsworth, J3-I, if present. Also acknowledge Garth Sanginiti as Chief of DPO Contracting, and Carol Sinnard and Debbie Young as contracting specialists and for their support, along with Michael Pardue, with registration and setup.
FOR OFFICIAL USE ONLY (FOUO)
| Opening Remarks | MG William Johnson, TCCS | |
| Team Introductions | Mr. Dean Peebels, TCAQ | |
| Program Overview | Mr. Dean Peebels, TCAQ | |
| Requirements Briefing | Col(S) Jackie Van Ovost, TCJ3-O | |
| 15 min Break | ||
| Performance Work Statement | Ms. Roni McDaniels, TCAQ | |
| Request for Proposal | Ms. Lisa Gross, TCAQ | |
| Small Business Participation | Ms. Michelle Mendez, TCAQ | |
| Questions / Closing Remarks | Mr. Dean Peebels, TCAQ |
USTRANSCOM
Agile Transportation for the 21st Century (AT21)
INDUSTRY DAY
PROGRAM OVERVIEW
31 OCT 2006
Briefer: Mr Dean Peebels, TCAQ, AT21 Program Manager
BACKGROUND
| Advanced Concept Technology Demonstration (ACTD) conducted 2003-2005 in partnership with DISA |
| Demonstrated utility of COTS supply chain management tools for |
collaboration, controlled business processes, and optimization/scheduling in support of deployment planning processes
| ACTD transition resulted in: |
| Implementation of TransViz tool to provide collaborative TPFDD |
visualization and analysis Focus Warfighter initiative – USTRANSCOM organizational realignment and business process transformation New acquisition – AT21 program approved by DUSD(AS&C) and registered with OSD comptroller as new start
| TransViz |
| Currently implemented at USTRANSCOM DDOC, CDDOC, and AMC(XOP) |
| Will be implemented at USCENTCOM (Tamp) in FY07 |
Outcomes:
| Aim | |
| Improve on time delivery | |
| Improve logistics lead times | |
| Standardize business rules globally | |
| Improve asset use across all modes | |
| Bring cost into decision making process | |
| Improve information sharing and decision making speed | |
| Reduce inventory handling | |
| Achieve | |
| Best case throughput capacity | |
| Improved force projection | |
| Customer confidence |
Background: TCDC directed J3 to come back with operational requirement for AT21. J3 has scaled-back the overall requirement to support critical capability shortfalls within a near-term 3 yr timeline and lower required funding levels.
Outcomes:
| Aim | |
| Improve on time delivery | |
| Improve logistics lead times | |
| Standardize business rules globally | |
| Improve asset use across all modes | |
| Bring cost into decision making process | |
| Improve information sharing and decision making speed | |
| Reduce inventory handling | |
| Achieve | |
| Best case throughput capacity | |
| Improved force projection | |
| Customer confidence |
Background: TCDC directed J3 to come back with operational requirement for AT21. J3 has scaled-back the overall requirement to support critical capability shortfalls within a near-term 3 yr timeline and lower required funding levels.
Outcomes:
| Aim | |
| Improve on time delivery | |
| Improve logistics lead times | |
| Standardize business rules globally | |
| Improve asset use across all modes | |
| Bring cost into decision making process | |
| Improve information sharing and decision making speed | |
| Reduce inventory handling | |
| Achieve | |
| Best case throughput capacity | |
| Improved force projection | |
| Customer confidence |
AT21 PROGRAM SCOPE
| Modernize deployment and distribution planning business processes and provide decision support tools that produce optimal intermodal distribution solutions to drive efficiencies: |
| Increment 1 Rqmts Consolidation and Workflow Mgt |
| USTRANSCOM funded and approved |
| Increment 2 Strategic Level Optimization & Scheduling |
| Not yet funded or approved |
| Increment 3 Operational Level Optimization & Scheduling |
| Not yet funded or approved |
Anticipate Joint Staff JROC approval for AT21 as ACAT III program designated JROC Interest
INCREMENT I OBJECTIVE
Increment I Focus Requirements
COP
FACTS
(airlift clearance) JOPES (Exercise) JOPES (Deployment)
CAMPS (SAAM)
JALIS (OSA)
Opportune Sustainment Transactions (IDE/GTN Feeds) Workflow Mgt
| Business Rules |
| Exception Mgt |
| Alert Notification |
Distribution Planning
| All Requirements |
| Lift Capacity |
| Collaboration |
| Adaptive |
Execution Schedules JOPES (Adaptive Plans) For the COCOMs
| Increased capacity/throughput |
| Improved on-time delivery |
| Automated business rules/data quality checks |
| Full requirements visibility |
For the Services
| Decreased transportation costs |
| Automated business rules/data quality checks |
| Requirements confirmation/notification |
| Full requirements visibility |
An initial task is to collect requirements from all sources and get them into a common set of data fields, in a single database.
Minimum process standards:
| Capability to receive and process customer requirements by phone, fax, e-mail, and EDI |
| Web-based requirement entry for select partners |
| Export and customs checks for denied parties |
Typical best practice processees
| Use of EDI and/or web-enabled requirement management to allow remote requirement entry, configuration management, order status updates |
| Transportation options and pricing included at requirement entry |
PROGRAM STATUS
Brief JS FCB/JCB Nov/Dec 06
G USTRANSCOM approved FY07-09 funding for Increment I Outyears partially funded, but require USTRANSCOM CIO program review and approval G G G Milestones (S)
| JROC CDD Approval Dec 06 | |
| Milestone B Decision | Dec 06 |
| Final RFP Release | Jan 07 |
| Contract Award | Jul 07 |
Funding/Cost (C) Next Steps
| Draft RFP released 19 Oct 06 |
| CDD completed initial joint staffing review with no issues |
Completed
RISK ASSESSMENT
| IDENTIFICATION | IMPACT | RISK MITIGATION |
| JROC does not approve CDD prior to Milestone B decision targeted for 15 Dec 2006 | Day-for-day delay in achieving capability delivery | Senior leaders maintain dialogue with JS to ensure timely staffing & approval |
| JROC designates program as JROC Interest | Increased program review and coordination will delay deliverables and milestones | No mitigation – OASD(NII) assigns MDA for program, but may delegate to USTRANSCOM |
| Lack of active operator participation throughout design, development, testing & implementation activities | Cannot achieve desired capability--program fails | Brief J3 quarterly and J3 division chiefs monthly to ensure continued AO participation |
| Unable to deliver capability in time to support standup of the Joint Operations Center (JOC) | Diminished effectiveness with reduced resources (post-BRAC); loss of customer confidence | Field capability in small spirals throughout Increment 1 to ensure initial operational capability prior to JOC standup |
| Unable to obtain funding for Increments 2 and/or 3 | Cannot achieve desired capability – reduced effectiveness and payback | Restructure increments into smaller, less costly capability spirals over longer timeframe |
PROGRAM TIMELINE
Increment 1 Pre-Milestone B Activities
Acquisition Incremental Capability Delivery (4 – 6 Spirals)
RFP
Release JROC Approval / Milestone Decision Exit Criteria:
| JROC-approved CDD |
| Economic Analysis/ Justification |
| Acquisition Strategy |
Increment 2 Exit Criteria:
Fully tested & fielded capability spirals
Milestone Planning Contract Award Ongoing Sustainment Increment 3
Sustainment
Milestone Decision Milestone Decision Requirements Definition Milestone Planning Incremental Capability Delivery (4 – 6 Spirals) Incremental Capability Delivery (4 – 6 Spirals)
Capabilities
CY 2006/07
CY 2008/09
CY 2010/11
CY 2012/13
CY 2014/15
CY 2016
| 2006, Pre-Milestone B activities |
| 31 Jul 2006, CDD submitted for JROC approval |
| Mid Oct 2006, Industry Day |
| 15 Dec 2006, Milestone B Decision |
| 2 Jan 2006, RFP release |
| Feb 2007, Phase 1 Source Selection & Down Select |
| Apr 2007, Phase II Source Selection & Recommendation |
| Mid May 2007, Contract Award |
Project Management Office (PMO) Organizational Chart Program Manager (PM) Dean Peebels Deputy Program Manager Roni McDaniels Contracting Officer Lisa Gross Functional Manager LTC Darrell Gregg System Engineer John Daum (MITRE)
Contracting Team Terri Francouer Michael Pardue
Technical Manager CDR Joel Price
Supply Chain Advisor Stu Draper (MITRE)
AT21 Executive Board Program Management Office Distribution Operations & Plans
IPT
Program Management IPT
PEO
MDA
PM
Technical
IPT
| Prime contractor works with the AT21 deputy program manager to provide overall direction for the program and implement program management processes |
| IPTs are responsible for supporting the planning and execution of all activities on the program. Beyond leads and permanent members, membership will be established as needed for each increment and spiral of the program. |
| I do not think Roni & Dean have time to have a single IPT that does it all and that you need to distribute some of that workload. Accordingly, instead of a single IPT with three components, I gave you 3 IPTs (they’d have 3 separate leads assigned with responsibility) inside the SPO. I’d go with |
| Laurie & Jackie as co-chair of the Distribution Operations working group, |
| Roni as the chair of the program management working group (Dean’s also TCAQ deputy and will have times when he cannot devote himself to this), and |
| Another Government person—probably CDR Joel Price-- (supported by the TCAQ systems engineer) as the chair of the third. |
These 2 possibly non-TCAQ chairs would of course be part of the PM IPT, and all would operationally be part of the SPO with responsibility to the PM.
I’m a big fan of pushing down responsibility & authority down to lowest level. This helps do that by putting the responsibility and authority together in TCJ3 for the business process change (they’re the ones who have to live with it, and they’re the ones in the command responsible for it).
QUESTIONS?
| Opening Remarks | MG William Johnson, TCCS | |
| Team Introductions | Mr. Dean Peebels, TCAQ | |
| Program Overview | Mr. Dean Peebels, TCAQ | |
| Requirements Briefing | Col(S) Jackie Van Ovost, TCJ3-O | |
| 15 min Break | ||
| Performance Work Statement | Ms. Roni McDaniels, TCAQ | |
| Request for Proposal | Ms. Lisa Gross, TCAQ | |
| Small Business Participation | Ms. Michelle Mendez, TCAQ | |
| Questions / Closing Remarks | Mr. Dean Peebels, TCAQ |
Industry Day Requirements Overview
Col (Sel) Jacqueline Van Ovost, TCJ3-O
OVERVIEW
| Background |
| Value proposition |
| Evidence value proposition is reasonable |
| Requirements drill down |
Just Some Numbers Deployment (Annual)
| More than 590,000 people |
| More than 640,000 short tons; 14,198,000 Sq ft |
| 768 Origins |
| 826 Destinations |
| 331 Ports of embarkation |
| 314 Ports of debarkation |
Sustainment
| 32,000 truck loads/month |
| 9,000 containers/month |
| 10,000 463L pallets/month |
Total Mobility TCN Shipments 106,917 4% of Records Can’t be Determined 65% will return to JOPES ULN Analysis – July 2006
Chart2
Represents good Army TCN will return to JOPES (0 in 15th position and have a UIC and ULN)
Represents total AF, Marine, Navy Shipments (have ULN, but no UIC)
Represents non processed Army shipments (UIC, but no ULN) Includes Army PREPO
Represents non-processed shipment records (no ULN, service undetermined)
12-Jul-06
44436
24525
33297
Sheet1
SQL pull from GTN on the SU_ID field 23-Jul-03 20-Jan-04 23-Dec-04 8-Mar-05 12-Jul-06
8+H Total shipments with 0 in position 15 (both TCMD and ATCMD) 165517 172711 208188 207975 106917
2+B Shipments with 0 in position 15 that have a ULN in GTN 120074 131620 153315 164254 68961
5+E Shipments with 0 in position 15 that have a UIC in GTN 103839 144576 181176 176662 77733
Shipments with 0 in position 15 that have no ULN or UIC 42947 7334 7108 5797 4659
7+G Shipments with 0 in position 15 that have both a ULN and UIC 101343 112643 139819 141576 44436
3+C Shipments that have a ULN but do NOT have a 0 in position 15 2265 3033 4433 4228 71
6+F Shipments that have a UIC but do NOT have a 0 in position 15 3184 2929 6031 4983 1
GTN passes manifest data to JOPES GTN cannot passmanifest data to JOPES GTN passes manifest data to JOPES GTN cannot passmanifest data to JOPES GTN passes manifest data to JOPES GTN cannot passmanifest data to JOPES GTN passes manifest data to JOPES GTN cannot passmanifest data to JOPES GTN passes manifest data to JOPES GTN cannot passmanifest data to JOPES
Total mobility TCN shipments (0 in 15 character) 165517 100% 100% 100% 172711 100% 100% 100% 208188 100% 100% 100% 207975 100% 100% 100% 100% 100% 100%
Represents all shipments, all services (0 in 15th position, and have a ULN). Represents all AF, M, N shipments and all good Army TCN 120074 131620 153315 164254 68961
Represent Army TCNs that will return to JOPES (0 in 15th position and have a UIC and ULN) 101343 112643 139819 141576 44436
Represents total AF, Marine, Navy Shipments (have ULN, but no UIC : subtract out good Army shipments) 18731 18731 11% 18731 11% 18977 18977 13496 13496 22678 22678 24525 24525
Represents Army only shipments (only Army records have a UIC) 103839 103839 63% 144576 181176 176662 77733
Represent good Army TCN will return to JOPES (0 in 15th position and have a UIC and ULN) 101343 101343 61% 112643 112643 139819 139819 141576 141576 44436 44436
Represent non processing Army shipments (UIC, but no ULN) 2496 2496 2% 31933 31933 41357 41357 35086 35086 33297 33297
Represents non-processing shipment records (no ULN, service undetermined) 42947 26% 42947 26% 7334 7334 7108 7108 5797 5797 4659 4659
165517 120074 73% 45443 27% 172711 131620 39267 208188 153315 48465 207975 164254 40883 106917 68961 37956
Total mobility TCN shipments (0 in 15 character) 165517
Represent good Army TCN will return to JOPES (0 in 15th position and have a UIC and ULN) 101343
Represents total AF, Marine, Navy Shipments (have ULN, but no UIC) 18731
Represent non processed Army shipments (UIC, but no ULN) 2496
Represents non-processed shipment records (no ULN, service undetermined) 42947
23-Jul-03 20-Jan-04 23-Dec-04 8-Mar-05 12-Jul-06
Represents good Army TCN will return to JOPES (0 in 15th position and have a UIC and ULN) 101343 112643 139819 141576 44436
Represents total AF, Marine, Navy Shipments (have ULN, but no UIC) 18731 18977 13496 22678 24525
| Represents non processed Army shipments (UIC, but no ULN) | |||||
| Majority Army PREPO | 2496 | 31933 | 41357 | 35086 | 33297 |
Represents non-processed shipment records (no ULN, service undetermined) 42947 7334 7108 5797 4659
Total mobility TCN shipments (0 in 15 character) 165517 172711 208188 207975 106917
12-Jul-06
Represents good Army TCN will return to JOPES (0 in 15th position and have a UIC and ULN) 44436
Represents total AF, Marine, Navy Shipments (have ULN, but no UIC) 24525
| Represents non processed Army shipments (UIC, but no ULN) | ||
| Includes Army PREPO | 33297 |
Represents non-processed shipment records (no ULN, service undetermined) 4659
Total mobility TCN shipments (0 in 15 character) 106917
Sheet1
12-Jul-06
Sheet2
Sheet3
OPERATIONAL ENVIRONMENT
Before Focus Warfighter Contingency Focus Warfighter I & II Global
CENTCOM
EUCOM
PACOM
AMERICAS
Undisciplined Confusing Stovepiped Complex Inefficient Processes Manpower Intensive Deploy /Redeploy Exercise
SAAM
Sustain Focus Warfighter III
AMC
SDDC
JDDOC
DLA
MSC
Supported COCOMs Objective Pre-Focus Warfighter Lift Capacity Constraints Business Rules Centralized Requirements and Workflow Management
Adaptive Exception Management Action Officer Dependent
| Disciplined, Efficient Processes |
| Model Physical Network, |
Items Being Shipped, and Carrier Contracts/Capabilities
| Capture & Manage All Requirements |
| Workflow Management |
| Build Shipments/Loads |
| Build Trips |
| Book/Tender |
| Visibility/Event Management |
| Track/Trace/Audit |
| Reports & Analytics |
| Collaborative Environment |
Core Capabilities
I can look toward enemy, knowing the USTRANSCOM/DPO is watching my backside (Gen Schwartz, 4/11/06)
End to End
“Living” OPLANs 2 Yr -> 6 Month Cycle 12 Hour Time Sensitive
Requirements not being met:
Exception management reporting Single requirements view for the Warfighter Requirements confirmation System transaction monitoring
Requirements not being met efficiently:
Requirements capture Orders entered/combined into single database Web-based requirement entry (deployment, sustainment, exercise, humanitarian, etc) Data quality checks All pertinent dates and times include local zone or GMT flags for requirement processing center (DDOC), shipping (ITO/TO, DDC, units), and receiving locations KPI: 98% data accuracy at order level (level 6 in deployment) Load consolidation Current (manual) business processes Requirements assessment Transportation feasibility Strategic planning
These requirements not being met:
Exception management reporting Single requirements view for the Warfighter Requirements confirmation Manual order confirmation faxed or e-mailed to customer within same day of order receipt if received before local time 2 PM/10AM; next day if received after 2 PM, confirming requested date or advising best possible based on shipment and transportation standard Confirmation documents generated in local languages as may be required Order processing KPI: All queries from customers receive initial response within 2 hours and closure within 24 hours Transaction Monitoring Process in place to advise customer on or before scheduled ship date if ship date slips more than one day Real-time visibility for customer teams into cusotomer backlog, order status, scheduled shipments, customer segmentation, and current customer inventory positions Track and report actual ship date against planned ship date, and against cusotomer requested delivery date KPI: On-time delivery to commit, request Consolidation/Loading Build load in stop sequence Process in place to combine all open orders for single ship to within time window agreed upon by customer Load optimization and consolidation analysis performed Transportation Management System (TMS) Minimum: Routing guides (IDLs) provide direction regarding shipping lanes and carriers to be used Typical Best Practice: Automated TMS provide carrier selection and routing based on multiple criteria E-Commerce Delivery Web site accessibility—customer interface is easy to find and usually available with down time less than 3% Novice users may need some help, but experts manage satisfactorily Reference data Internal data validity: Data management process ensures all data are accurate before entry Customer data validity: Offline data management process ensures all customer data are current and accurate before processing. Errors found in customer data are corrected in database for future use.
FUTURE FUSION PROCESS
| Develop & Operate Responsive Mobility System |
| Transform the Way We Work Together |
Supplier locations Production Capacity National & COCOM Competing Requirements Costs Consumption Rates Sealift Capacity Airlift Capacity Commercial vs. Organic
EXECUTE
JOINT
AMC
SDDC
MSC
JTF-PO
JDDOC
PLAN
JOINT
AMC
SDDC
MSC
ASSESS
JOINT
AMC
SDDC
MSC
Planning Factors Directly supports JL (D) JIC shortfalls:
Conduct JDDE assess & plan, Control JDDE ops, Conduct JDDE perf analysis Requirements
COCOM-ORIENTED DIVISIONS
Transportation
CONOPS
Multi-modal End to End Detailed Tasking Exercise Sustainment
SAAM
Contingency IDLs/Channels
Under the Focus Warfighter initiative, we identified the need to obtain visibility over all requirements and consolidate requirements assessment and planning functions to more effectively support the Warfighter. To that end, we reorganized the DDOC and planned for the Fusion Center standup which will realign both our organizational structure and planning processes by consolidating duplicative functions across the HQ and component commands.
However, even with the realignment of people, organizational structure, and processes, we still have critical capability shortfalls because all of these processes are accomplished manually today.
Deployment Model
| Ensure ITV/Track Requirements |
| Share Knowledge / Feedback |
| Effective Events/Exception Handling |
| Financial/Contractual Perf Mgmt |
Strategic Activities Functions Requirement Planning Commitment Execution Delivery
| ID Requirement |
| Network Infrastructure |
| Threat Assessment |
| Initial Mode Selection |
| Refine Infrastructure |
| Threat Assessment |
| E2E Feasibility |
| Dynamic Replanning |
| Notional Sourcing |
| Infrastructure Analysis |
| Programmatic Support |
| Initial Feasibility / Cost |
| COA Development |
| Manage Events/Exceptions |
| Track Requirement |
| Planned vs Actual Req & Capacity |
| Customer Satisfaction |
| Dynamic Replanning |
Plan Initial Commitment Final Commitment Delivery of Commitment
| CONOP Selection |
| Threat Working Group |
| Final Req / Aggregation |
| Final Feasibility / Cost |
| Acquire Capacity / AQ / JA |
| ID Billpayer/Finance Rpt |
We are Transforming Today…
Units Nodes
J-DDOC
JTF-PO
Fulfill Commitment
TCCs
JDPAC
USA
JDDOC
COCOM
TCCs
USAF
USMC
USN
DM4-A
USTC
STAFF
JTF-PO
DM4-S
AT21 GOALS
| Satisfy JDDE, JL(D) JIC requirements |
| Increase deployment & distribution planning lead times & reduce customer response times |
| Improve information sharing / decision making speed |
| Reduce DoD distribution / throughput costs |
| Globally standardize business rules |
| Improve asset utilization across all modes |
| Introduce cost into decision making process |
The ideal: Once a requirement (an order) enters the system, the order and related people or cargo keep moving, minimizing unintended delay until its reach destination and accountability throughout the enterprise is achieved.
Satisfy BRAC requirements
| -- Being able to work through requirements (orders) faster enables doing same work with fewer people |
| -- Enables consolidation of C2 into coherent operation |
Improve delivery to warfighter
— Readiness drivers, especially Reduce DoD distribution costs Improve quality of life
-- HHG
| -- Part of JDDE |
| -- Not what we’re working on in AT21 at least for now!! DPS program working this! |
-- Crews
| -- Evidence from DARPA funded demonstration showed potential for 10% increase in aircrew availability/month while improving reliability of individuals’ schedules |
| -- Originally part of concept, but AT21 restricted by former J3’s direction to strategic and operational levels |
Increase the amount of time USTRANSCOM has to plan and coordinate movements of passengers and cargo Embed standardized business rules and processes in commercial software to ensure we do business the same way throughout the world Meet our customers’ demands using best mix of land, sea, and air transportation Efficiently use transportation assets, focusing on cost avoidance and asset availability Automatically communicate orders to those who will do the moving Increase the amount of time USTRANSCOM has to plan and coordinate movements of passengers and cargo Embed standardized business rules and processes in commercial software to ensure we do business the same way throughout the world Meet our customers’ demands using best mix of land, sea, and air transportation Efficiently use transportation assets, focusing on cost avoidance and asset availability Automatically communicate orders to those who will do the moving
Value Proposition Synchronized distribution operations address key DPO capability gaps:
Priority 1 Intransit Visibility Priority 2 Distribution Planning & Forecasting Priority 3 Joint Transportation Interface Priority 9 Cargo Booking Priority 20 Customer Service
Synchronized distribution operations can achieve these goals What it takes Processes
| -- Best practices | |
| — Leverage successful things others do | |
| -- Reliable, repeatable | |
| --Reliable: takes the same time and resources for every order; similar decisions; same result | |
| --Repeatable: every order done the same over and over |
Optimization
| -- Does the actual synchronizing across the supply chain | |
| -- BRAC enabler | |
| -- Can be decomposed at price of not so good solutions | |
| -- This is important advantage of consolidating DoD distribution planning! | |
| -- Central to choosing who should do what, when, while improving delivery, reducing cost, and improving quality of life |
Collaboration
| -- Several forms | ||
| -- To understand requirements | ||
| -- Synchronous, analytical collaboration best | ||
| -- TransViz fielding has begun for TPFDD type requirements | ||
| -- To form contracts | ||
| -- Usually serial, business process-oriented collaboration | ||
| -- Used | ||
| -- To tender requirements to TCCs, theater distribution operations, DLA(?) for execution | ||
| -- To book (reservations) and conclude contractual obligations with commercial partners |
AT21 ACTD MUA: Value Proposition Is Reasonable
| Improved delivery |
| 25% increase in planned on-time by air |
| 8% increase in planned on-time by sea |
| More effective load consolidation increased planned aircraft payloads |
| 9% for passengers and 8% for cargo |
| AT21 payback expected: development, fielding, and O&M costs several times over |
| Independent, 3rd party analysis based on military utility assessment run in parallel with actual deployment operations in October-November, 2004\ |
| 25% increase in planned on-time delivery by air and an 8% increase in planned on-time delivery by sea |
| More effective load consolidation increased planned aircraft payloads by 9% for passengers and 8% for cargo |
| For the USCENTCOM AOR (6 deployment TPFDD only) the cost avoidance was projected during the ACTD’s MUA to exceed $40 million a year. |
| Total USTRANSCOM contingency operating costs from FY06 through FY15 are forecast to be $64 billion. The improved effectiveness and efficiency over this period are estimated very conservatively to exceed $1.8 billion. The current budget estimate to field and operate AT21 capabilities is approximately $90 million. Over the life cycle of current technology, and accounting for the uncertainty in estimates, the median benefit-cost ratio to be realized by the AT21 system is 17, which means AT21 is expected to pay back 17 times its investment cost over the 10 year period. |
| These benefits can be explained by the following observations regarding the AT21 system. |
| The AT21 system demonstrated that it can generate transportation plans significantly quicker than the incumbent system, enabling system users to implement those plans sooner and respond to planning changes sooner. |
| The automated processing within AT21 allows action officers to focus their efforts on exception processing rather than routine processing thus allowing action officers to be more productive. |
| Increased staff efficiency requiring an expected 30% less effort will free action officer time for more detailed analysis of requirements and plans and for other tasks. |
| AT21’s TransViz collaboration tool demonstrated the potential, through effective collaboration, to allow analysts in different locations to share information more effectively, generating better transportation plans due to better understanding of requirements and easier agreement regarding changes to an existing plan. |
AT21 Scope—SCOR Perspective © Copyright 2006 Supply-Chain Council
Source: Supply Chain Council
High-Level Information Architecture Flow with Major Systems
MRO
CCP
DEPOT
BASE
TDC/MCT
Tactical Assembly Area/BASE Service Supply Activity
POE
POD
THEATER
DEPOT
EMPLOYMENT AREA
REQ
AT21 – Transformation: Process & Systems
POINT OF EFFECT
AT21 Operating Environment
COCOMs
JDDOCs
JOPES
AT21 (USTRANSCOM DDOC)
AT21 - Notional System Environment
IGC
Optimized Movement Plans
Optimized Movement Plans
Lift Asset Availability Information
Transportation Plan Visibility
DLA / Services
Sustainment Requirements
NATIONAL
PARTNERS
Distribution Node Availability Information
Commercial
Optimized Movement Plans
Lift Asset Availability Information
Distribution Node Availability Information
SIPRNET
Execution
Exception
Information
Optimization
Process Control
Collaboration
(TRANSVIZ)
Time-Phased Schedule Variance Information
Contingency Requirements
High Level Data Flow KEY
Movement Requirements
Availability Information
Contingency Requirements
Sustainment Requirements
Optimized Movement Plans
Transportation Plan Visibility
Time-Phased Schedule Variance Information
Movement Requirements
ACFP
CAMPS
GATES
GDSS
IBS
IC3
IBS
GFM
WPS
TCCs
SDDC
MSC
AMC
The Systems Communications Description depicts pertinent information about communications systems, communications links, & networks. The SV-2 documents the kinds of Comm media that support the systems.
Other addresses those systems that would generate Movement Requirements such as those from GSA, DECA, Joint Munitions Command
AT21 Requirements--Order Management Shortfalls
| Requirements Capture |
| Collaboration with customers to better understand requirements (orders). |
| Orders entered into single database |
| Web-based order entry |
| Requirements Commitment Confirmation |
| Manual order confirmation faxed or e-mailed to customer within same day of order receipt if received before local time 2 PM/10AM; next day if received after 2 PM, confirming requested date or advising best possible based on shipment and transportation standard |
| Order Processing & Exception Management Reporting |
| Transaction Monitoring |
| Process in place to advise customer on or before scheduled ship date if ship date slips more than one day |
| Real-time visibility for customer teams into customer backlog, order status, scheduled shipments, customer segmentation, and current customer inventory positions |
| Track and report actual ship date against planned ship date, and against customer requested delivery date |
| Requirements capture |
| Orders entered into single database |
| Web-based order entry |
| Export order checks |
| All pertinent dates and times include local zone or GMT flags for processing center, shipping, and customer locations |
| KPI: 98% data accuracy at order level (level 6 in deployment) |
| Requirements confirmation |
| Manual order confirmation faxed or e-mailed to customer within same day of order receipt if received before local time 2 PM/10AM; next day if received after 2 PM, confirming requested date or advising best possible based on shipment and transportation standard |
| Confirmation documents generated in local languages as may be required |
| Order processing |
| KPI: All queries from customers receive initial response within 2 hours and closure within 24 hours |
| Transaction Monitoring |
| Process in place to advise customer on or before scheduled ship date if ship date slips more than one day |
| Real-time visibility for customer teams into customer backlog, order status, scheduled shipments, customer segmentation, and current customer inventory positions |
| Track and report actual ship date against planned ship date, and against customer requested delivery date |
| KPI: On-time delivery to commit, request |
| Exception management reporting |
AT21 Requirements--Order Management Planned Capability
| Requirements Capture |
| Ability to differentiate between forecasted and actual demand |
| KPI: 98% data accuracy at order level (level 6 in deployment and item level for distribution) |
| Requirements Commitment Confirmation |
| Manual order confirmation faxed or e-mailed to customer within same day of order receipt |
| Order Processing & Exception Management Reporting |
| KPI: All queries from customers receive initial response within 2 hours and closure within 24 hours |
| 3 R’s: Repeatable, Reproducible, and Reliable |
| Transaction Monitoring |
| KPI: On-time delivery to commit |
Focus: Movement Requirements Capture & Tracking; Measurable, Reliable, Repeatable Steps to Develop Itineraries, Plan Missions, and Execute Schedules
| Requirements capture |
| Orders entered into single database |
| Web-based order entry |
| Export order checks |
| All pertinent dates and times include local zone or GMT flags for processing center, shipping, and customer locations |
| KPI: 98% data accuracy at order level (level 6 in deployment) |
| Requirements confirmation |
| Manual order confirmation faxed or e-mailed to customer within same day of order receipt if received before local time 2 PM/10AM; next day if received after 2 PM, confirming requested date or advising best possible based on shipment and transportation standard |
| Confirmation documents generated in local languages as may be required |
| Order processing |
| KPI: All queries from customers receive initial response within 2 hours and closure within 24 hours |
| Transaction Monitoring |
| Process in place to advise customer on or before scheduled ship date if ship date slips more than one day |
| Real-time visibility for customer teams into customer backlog, order status, scheduled shipments, customer segmentation, and current customer inventory positions |
| Track and report actual ship date against planned ship date, and against customer requested delivery date |
| KPI: On-time delivery to commit, request |
| Exception management reporting |
CDD Requirements-Order Management
| Well-understood, fully documented, and standardized movement requirements management and distribution planning processes that are repeatable, reproducible, and reliable | 80% Assessments Completed, Fully Socialized, and Transferable to New IT Support Capability | 99% Assessments Completed, Fully Socialized, and Transferable to New IT Support Capability |
| Generate information into a configurable collaborative environment that displays improved C2 situational awareness/decision-ready movement tracking information | Ability to track processing of 99.73% (3-Sigma) all available movement requirements based on accessible data sources | Ability to track processing of 99.9999998% (6-Sigma) all available movement requirements based on accessible data sources |
| Assignment of a unique transportation tracking number | Ability to reconstruct a single order with a single tracking number, 99.73% (3-Sigma) of the time | Ability to reconstruct a single order with a single tracking number, 99.9999998% (6-Sigma) of the time |
| Requirements data capture and requirements management work flow to facilitate visibility over all movement requirements, intermodal analysis and asset management decision-making | Percent of transactions not requiring additional human-computer or manual input, 99.73% (3-Sigma) of the time | Percent of transactions not requiring additional human-computer or manual input, 99.9999998% (6-Sigma) of the time |
| Collaborate with the Warfighter (customer) to select and validate the service level that best supports the requirement | Degree to which the relevant information enabled proactive action (before the event decision was required), 99.73% (3-Sigma) of the time: |
Air: 7 Days Sea: 30 Days Surface: 7 Days Degree to which the relevant information enabled proactive action (before the event decision was required), 99.9999998% (6-Sigma) of the time:
Air: 7 Days Sea: 75 Days (or less than the time required to contract for sealift) Surface: 2 Days
Threshold Objective
AT21 Requirements--Optimization Shortfalls Increments 2 & 3
| Consolidation/Loading |
| Build load in stop sequence |
| Process in place to combine all open orders for shipment to destination within time window agreed upon by customer |
| Load optimization and consolidation analysis performed |
| Routing, including modes |
| Commitment appointments throughout DPO execution domain |
| Transportation Management System (TMS) |
| Minimum: Routing guides (IDLs) provide direction regarding shipping lanes and carriers to be used |
| Typical Best Practice: Automated TMS provide carrier selection and routing based on multiple criteria |
AT21 Requirements--Optimization Planned Capability, Increments 2 & 3 Optimization and Scheduling, COCOM Deployment and Implementation, Infrastructure Flow Management, and Robust Costing Options
Create origin-destination movement plans for all COCOMs, USTRANSCOM plan tasking to TCCs for exectution, and coordination with COCOMs Link planning asset visibility requirements information to globally optimized execution schedules Up-front end-to-end service level costing options for the Warfighter Global infrastructure flow management (i.e. port availability and throughput, weather, etc.)
Capture delivery track, trace, and audit information for the selected movement alternative Support operational maneuver across global distances and tactical maneuver throughout a regional COCOM’s area of responsibility (AOR) through creation of operational movement schedules Seamless visibility of the distribution process flow while improving the efficacy of the execution schedules and business rules to achieve perfect order fulfillment Capture fused intelligence planning and operational information and apply appropriate DPO pipeline throughput constraints, business rule changes, and execution schedule exception management actions to the optimization process.
Focus: Ability to Make Deployment & Fulfillment Commitments and Deliver On Those Commitments
A promise made is a promise kept!
CDD Requirements—Increment 2
| Create strategic movement plans for USCENTCOM only, USTRANSCOM plan tasking to TCCs, and coordination with USCENTCOM and USJFCOM | 95% line items in the plan that are executable by mode operators or third party logistics agents | 99% line items in the plan that are executable by mode operators or third party logistics agents |
| Simultaneously plan a set of strategic, operational, and tactical level requirements using all primary variables necessary to ensure each order is delivered on time, at the right place, and – if the other criteria are met – for the lowest cost; and select and allocate sealift-qualified movement requirements to increase availability of scarce airlift assets, reduce costs, and optimize mission critical movement requirements | Percent of transactions not requiring additional human-computer or manual input, 99.73% (3-Sigma) of the time | Percent of transactions not requiring additional human-computer or manual input, 99.9999998% (6-Sigma) of the time |
| Create strategic movement plans, USTRANSCOM plan tasking to TCCs, and coordination with COCOMs | 95% line items in the plan that are executable by mode operators or third party logistics agents | 99% line items in the plan that are executable by mode operators or third party logistics agents |
| Service Commitment Cost and Delivery Alternatives: Up-front end-to-end costing options presented transparently to the Warfighter or designated agent for selection | Customer selects one of the alternative service commitment cost options presented without recommending a separate alternative 90% of the time | Customer selects one of the alternative service commitment cost options presented without recommending a separate alternative 95% of the time |
| Link planning asset visibility requirements information to the globally optimized execution schedule and deliver the information to the appropriate modal execution system | Percent of transactions not requiring additional human-computer or manual input, 99.73% (3-Sigma) of the time | Percent of transactions not requiring additional human-computer or manual input, 99.9999998% (6-Sigma) of the time |
Threshold Objective
CDD Requirements—Increment 3 Threshold Objective
| Support operational maneuver across global distances and tactical maneuver throughout a regional combatant commander’s AOR by creation of operational movement schedules | 95% line items in the plan that are executable by mode operators or third party logistics agents | 99% line items in the plan that are executable by mode operators or third party logistics agents |
| Seamless visibility of the distribution process flow, while improving the fidelity of the business rules, processes, and algorithms that facilitate intermodal analysis and asset management decision-making | Percent of transactions not requiring additional human-computer or manual input, 99.73% (3-Sigma) of the time | Percent of transactions not requiring additional human-computer or manual input, 99.9999998% (6-Sigma) of the time |
| Global deployment/distribution plan within the USTRANSCOM operations center and successfully tender and coordinate the applicable elements of that plan to the three Transportation Component Commands for tactical execution within the global distribution environment; with theater tactical level optimization and scheduling; and a single unified JDDE capable of rapidly delivering and positioning joint forces and collaborative sustainment from any origin or supply source to any JFC designated point of need and back again | 95% line items in the plan that are executable by mode operators or third party logistics agents | 99% line items in the plan that are executable by mode operators or third party logistics agents |
| Operate in an integrated and synchronized distribution and deployment process that provides consistent, increasingly more effective and efficient operations and meets warfighter (customer) requirements; with Optimized, controlled distribution processes that employ advanced, globally networked tools and techniques in every echelon of the DPO | Degree to which 50% of reference information is available for electronic (e.g., EDI, etc.) input or retrievable from an automated source; and the relevant information enabled proactive action (before the event decision was required), 99.73% (3-Sigma) of the time. | Degree to which 85% of the reference information is available for electronic (e.g., EDI, etc.) input or retrievable from an automated source; and the relevant information enabled proactive action (before the event decision was required), 99.9999998% (6-Sigma) of the time. |
Operational Benefits
Simplified submission and processing of COCOM requirements
Improved/compressed forecasting and planning capability/process
Improved common operational picture of lift assets/availability
Increased mode determination effectiveness and flexibility
Enabling the C2 Environment
Responsive, dynamic capability to anticipate and resolve distribution challenges
Enhanced C2, intransit visibility, onward movement planning and execution for all missions
The Focus Warfighter initiative has identified 4 operational benefits expected as a result of consolidated planning processes in the Fusion Center.
A scaled-back AT21 initiative will directly support automation and additional process improvements for 3 of these 4 planning processes.
There are a lot of moving parts! Any questions about requirements?
| Opening Remarks | MG William Johnson, TCCS | |
| Team Introductions | Mr. Dean Peebels, TCAQ | |
| Program Overview | Mr. Dean Peebels, TCAQ | |
| Requirements Briefing | Col(S) Jackie Van Ovost, TCJ3-O | |
| 15 min Break | ||
| Performance Work Statement | Ms. Roni McDaniels, TCAQ | |
| Request for Proposal | Ms. Lisa Gross, TCAQ | |
| Small Business Participation | Ms. Michelle Mendez, TCAQ | |
| Questions / Closing Remarks | Mr. Dean Peebels, TCAQ |
| Opening Remarks | MG William Johnson, TCCS | |
| Team Introductions | Mr. Dean Peebels, TCAQ | |
| Program Overview | Mr. Dean Peebels, TCAQ | |
| Requirements Briefing | Col(S) Jackie Van Ovost, TCJ3-O | |
| 15 min Break | ||
| Performance Work Statement | Ms. Roni McDaniels, TCAQ | |
| Request for Proposal | Ms. Lisa Gross, TCAQ | |
| Small Business Participation | Ms. Michelle Mendez, TCAQ | |
| Questions / Closing Remarks | Mr. Dean Peebels, TCAQ |
Draft Performance Work Statement (PWS) Overview Ms. Roni McDaniels
USTRANSCOM/TCAQ
Deputy Program Manager
Increment 1 Requirements Consolidation and Work Flow Management (36 Months) Increment 2 Increment 3 Implementation Approach
Strategic Level Optimization and Scheduling (36 Months) Operational Level Optimization and Scheduling (36 Months) Post Support Post Increment 3 Transition Support (12 Months)
| The IT Interface and testing are the first milestones on the critical path. |
| Without the automated interfaces, the DLA warehouse operations can not afford the time required to utilize the Coordinator services effectively. |
| So Shipping with the Coordinator will not begin until the IT integration test are complete. |
Primary Task Areas
| Project Management |
| Design, Development, and Deployment |
| Interim Contractor Support |
Project Management Task Area
| Work Breakdown Structure (WBS) |
| Earned Value Management |
| Resource-loaded Integrated Master Schedule |
| Cost Performance Report monthly |
| Integrated Baseline Reviews (IBRs) |
| Technical Interchange Meetings (TIMs) |
| Monthly In-Process Reviews (IPRs) |
Design, Development, and Deployment Task Area
| Business Process Improvement |
| Systems Engineering |
| Spiral Capability Design |
| Systems Engineering Processes |
| Staffing |
| Standards |
| Test & Implementation |
Will add notes to address primary points under each bullet
Task Area
| Business Process Improvement |
| End-to-end solution blueprint |
| Business process reengineering |
| Change management |
Task Area
| Systems Engineering |
| End-to-end architecture design |
| Spiral capability design |
| System Requirements Review (SRR) |
| Critical Design Review (CDR) |
| Systems Engineering Processes |
| Reference data management |
| Verification and validation testing |
| Technical reviews (SRR, CDR, TRR) |
| Configuration Control Board (CCB) |
| Integrated Product Teams (IPT) |
| Measures |
Task Area
| Standards |
| Joint Distribution Architecture |
| Data standardization in compliance with USTRANSCOM Master Model |
| Logical Data Model |
| JITC interoperability certification |
Task Area
| Test & Implementation |
| Operational Test & Evaluation |
| User Training |
| Capability Deployment |
| Software Problem Resolution |
Interim Contractor Support Task Area
| Help Desk (Tier 2/3) |
| 24x7 on call support |
| Software Maintenance Support |
| Software version upgrades |
| Software |
Call us at (618)256-4300 or Email the AT21 PMO at at21@ustranscom.mil
Thanks Questions?
| Opening Remarks | MG William Johnson, TCCS | |
| Team Introductions | Mr. Dean Peebels, TCAQ | |
| Program Overview | Mr. Dean Peebels, TCAQ | |
| Requirements Briefing | Col(S) Jackie Van Ovost, TCJ3-O | |
| 15 min Break | ||
| Performance Work Statement | Ms. Roni McDaniels, TCAQ | |
| Request for Proposal | Ms. Lisa Gross, TCAQ | |
| Small Business Participation | Ms. Michelle Mendez, TCAQ | |
| Questions / Closing Remarks | Mr. Dean Peebels, TCAQ |
Draft Solicitation Overview
Ms. Lisa Gross
USTRANSCOM/TCAQ
Contracting Officer 31 October 2006
Today’s Brief
| Draft Solicitation Highlights |
| FAR Part 15 – Contracting By Negotiation |
| Section A through Section M |
| Source Selection Approach |
| Key Dates |
| Draft Solicitation Questions |
Draft Solicitation Highlights
| Cost plus Award Fee (CPAF) |
| Cost-Reimbursement for Development |
| Cost-Reimbursement for Operations and Maintenance |
| Cost-Reimbursement Other Direct Costs (Hardware and Software Purchases) |
| Award Fee Provisions to Motivate Superior Performance |
| Potential 10-Year Contract Life Cycle |
| 1-year Base Period |
| Nine 1-year Options |
Encourages Small Business Participation
Draft Solicitation Highlights (Continued)
| Performance Based Work Statement |
| Best Value Competitive Process |
| Using Multi-Step Evaluation Process |
| Uniform Contract Format – Section A through M |
FAR Part 15 - Contracting By Negotiation
| Part I - The Schedule |
| Section A - Solicitation/Contract Form |
| Section B – Supplies or Services and Prices/Costs |
| Section C - Description/Specifications/Performance Work Statement |
| Section D - Packaging and Marking |
| Section E - Inspection and Acceptance |
| Section F - Deliveries or Performance |
| Section G - Contract Administration Data |
| Section H - Special Contract Requirements |
FAR Part 15 - Contracting By Negotiation (Continued)
| Part II – Contract Clauses |
| Section I - Contract Clauses |
| Part III - List of Documents, Exhibits, and Other Attachments |
| Section J - List of Attachments |
| Part IV - Representations and Instructions |
| Section K – Representations, Certifications, and Other Statements of Offerors |
| Section L - Instructions, Conditions, and Notices to Offerors or Respondents |
| Section M - Evaluation Factors for Award |
Section A - Contract
| Standard Form 33 |
| Block 9 - Place & Time for Receipt of Offerors |
| Complete All Required Blocks [13 -18] |
Acknowledge Receipt of Amendments Name, Title, Signature of Authorized Agent
Section B - Pricing
| Line Items Priced in Three Increments |
| Same Contract Line Item Number (CLIN) Structure for Each Increment |
| CLIN for AT21 Development |
| CLIN for AT21 Operating and Maintenance |
| CLIN for Other Direct Costs |
| CLIN for Travel |
| CLIN for Award Fee |
Allowable Cost and Payment Provisions – Infuses Accountability through Post Payment Audit
Section B - Pricing (Continued)
| Other Direct Costs |
| CLIN Established for the Purchase of Hardware or Software Required to Support the AT21 IT Implementation Plan |
| Any Hardware or Software Requirements Identified After Contract Award Require Approval from the Program Manager PRIOR TO PURCHASE |
Section B - Pricing (Continued)
| Base Fee |
| Base Fee Established by Government at 0% |
| Award Fee |
| Motivate Superior Performance IAW the Award Fee Criteria Established |
| Contractor Can Earn up to 100% of the Award Fee as Determined by the Government Fee Determining Official |
| Contractor Invoices for Amount of Award Fee Earned |
| Award Fee Established at a Maximum of 10% of the Development Dollars |
Section C – Performance Work Statement
| Performance-Based Requirements |
| Managed in Increments |
| Increment I – Requirements Consolidation and Workflow Management |
| Increment II – Strategic-Level Optimization and Scheduling |
| Increment III – Operational-Level Optimization and Scheduling |
| Post Increment III – Post Increment III Support |
| Initiation of Each Increment is not Necessarily Dependent on the Completion of the Previous Increments. |
| Performance Objectives and Deliverables are Listed in the PWS |
Section D – Packaging & Marking Packaging and Marking IAW Standard Commercial Practices unless Otherwise Specified in PWS
Section E – Inspection and Acceptance
| FAR 52.246-5, Inspection of Services – Cost-Reimbursement (Apr 1984) |
| Inspection and Acceptance Will Take Place at USTRANSCOM or the Contractor’s Facility |
| Inspection and Acceptance to be Performed by the Contracting Officer’s Representative (COR) as Designated by the Contracting Officer |
Section F – Deliveries or Performance
| Period of Performance | ||
| Increment I | 36 Months | |
| Increment II | 36 Months | |
| Increment III | 36 Months | |
| Post Increment III | 12 Months | |
| Government Anticipates 4-6 Spiral Capability and Process Releases Within Each of the Three Major Increments |
| Period of Performance | ||
| Increment I, Year 1 | 1 Jul 07 – 30 Jun 08 | |
| Increment I, Year 2 | 1 Jul 08 – 30 Jun 09 | |
| Increment I, Year 3 | 1 Jul 09 – 30 Jun 10 | |
| Increment II, Year 1 | 1 Jul 10 – 30 Jun 11 | |
| Increment II, Year 2 | 1 Jul 11 – 30 Jun 12 | |
| Increment II, Year 3 | 1 Jul 12 – 30 Jun 13 | |
| Increment III, Year 1 | 1 Jul 13 – 30 Jun 14 |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .