1. 2. Question and Answers 2.1 Follow-up on Open Items
2.2 Implementation Scope Review
2.3 Implementation Schedule Activities
2.4 Open Q&A

2. 2.1 Follow-up on Open Items

3. 2.2 Implementation Scope

4. Implementation Scope – Phase 1

5. Implementation Scope – Phase 2

6. Integration

7. Data Migration Validate Process (e.g., subset) Schedule Full Migration
Validation
Migration
Planning
Assessment
Validate Process (e.g., subset)
Schedule Full Migration

8. 2.3 Implementation Schedule Activities

9. Methodology / Approach / Configuration
Kickoff
Discovery
Design
Configure
Test
Train
Adoption
Reviewed Implementation Phases
Currently in Kick-off
Will move to Discovery Phase – Objectives – fundamental understanding of e-Builder – what does NJDOT want e-Builder to do – understand what e-Builder will do at the 30K level – second objective – why does NJDOT do business the way they do – how/why/requirements – lot of Q&A – sample documents – diagrams – workflows – fundamental to this process is core team
When will start using e-Builder? – implementation in e-Builder – NJDOT will be active e-Builder users – Core Team – s will be minimal – will have an implementation dashboard – all documents will be in an e-Builder document structure – receive value from e-Builder today
Mix of onsite and remote sessions – where most effective
Meeting Minutes taken in e-Builder and issued through e-Builder
Build what we understand
Design
Done on site
Give NJDOT an idea of what e-Builder will be building
Documentation and prototyping
White boarding
Discussion
Process Requirements
Solution Document
Deliverables
Adoption Plan – how ever many phases equals how many adoption plans – how will we test this? – Sign off on adoption plan – NJDOT will be held accountable to Adoption Plan deliverables – in time frame allotted for Adoption Plan
Custom Development Requirements
Integration Requirements
Design Session – 3 days – agenda will be delivered to NJDOT – hourly based – allows for SMEs to come into Design Meetings – 2 week notice to plan and schedule Design topics – 8 hours a day for T, W, and Th – no questions
Configuration
Breather for NJDOT
Will have BETA2 site as well
e-Builder is now building items that came out of Design session
Account Config
Internal Testing
Testing
UAT – take NJDOT data and NJDOT users and drive system – use script – will model a normal transaction – need to provide real-world NJDOT data
Client Acceptance Letter – Scope met – item complete – ready to train and roll-out
UAT will be done onsite – not a full team involvement – e-Builder will not do the driving – NJDOT users will be entering data
Testing – Unit testing or System Wide testing – Unit inside of phase testing – if first phase is Document testing – individual usage testing of document testing – as well as testing of entire document management feature – will not go back to documents to retest when a new feature is being rolled out – test cases – who will prepare them? – prepared as a team – e-Builder to NJDOT – test scripts will be provided to NJDOT
Trainers will be Austin and Bryon – Training is not outsourced – done by BAs – three different types of training – team approach for Admin Training – NJDOT will be able to write their own forms – workflows – etc. – not just maintain current system – it’s the entire system – enhancing e-Builder for future
Users – NJDOT users and external users –
Training Guides
User Guides
All training – except for online refreshers – will be done onsite – electronic PDF copies – expectation for NJDOT – is a training location – and sitting in front of a computer – users will need to bring in real NJDOT data –
Adoption
Adopt what was laid out in adoption document
Question on the Floor – electronic invoicing – who will be delivering the training to NJDOT users – someone said that it is close to being done today – electronic invoicing
Will address any feedback that comes out of adoption period – combo of remote sessions and onsite support
Out of Adoption – will be phase transitions – phase transitions will overlap
Will have a final transition to Account Management staff – this will be the PoC for rest of e-Builder time

10. Discovery Calls & Onsite
Kickoff
Discovery
Design
Configure
Test
Train
Adoption
Objectives
Clear definition of current state
Clear definition of current challenges
Required Resources
PSU Core Team
PSU SME’s
Deliverables
Discovery call Meeting Minutes
Sample documents from PSU
Sample documents of e-Builder Enterprise forms.
Discovery Calls & Onsite
#1 Overview
#2 Roles & Permissions
#3 Folders
TBD based on implementation approach
Reviewed Implementation Phases
Currently in Kick-off
Will move to Discovery Phase – Objectives – fundamental understanding of e-Builder – what does NJDOT want e-Builder to do – understand what e-Builder will do at the 30K level – second objective – why does NJDOT do business the way they do – how/why/requirements – lot of Q&A – sample documents – diagrams – workflows – fundamental to this process is core team
When will start using e-Builder? – implementation in e-Builder – NJDOT will be active e-Builder users – Core Team – s will be minimal – will have an implementation dashboard – all documents will be in an e-Builder document structure – receive value from e-Builder today
Mix of onsite and remote sessions – where most effective
Meeting Minutes taken in e-Builder and issued through e-Builder
Build what we understand
Design
Done on site
Give NJDOT an idea of what e-Builder will be building
Documentation and prototyping
White boarding
Discussion
Process Requirements
Solution Document
Deliverables
Adoption Plan – how ever many phases equals how many adoption plans – how will we test this? – Sign off on adoption plan – NJDOT will be held accountable to Adoption Plan deliverables – in time frame allotted for Adoption Plan
Custom Development Requirements
Integration Requirements
Design Session – 3 days – agenda will be delivered to NJDOT – hourly based – allows for SMEs to come into Design Meetings – 2 week notice to plan and schedule Design topics – 8 hours a day for T, W, and Th – no questions
Configuration
Breather for NJDOT
Will have BETA2 site as well
e-Builder is now building items that came out of Design session
Account Config
Internal Testing
Testing
UAT – take NJDOT data and NJDOT users and drive system – use script – will model a normal transaction – need to provide real-world NJDOT data
Client Acceptance Letter – Scope met – item complete – ready to train and roll-out
UAT will be done onsite – not a full team involvement – e-Builder will not do the driving – NJDOT users will be entering data
Testing – Unit testing or System Wide testing – Unit inside of phase testing – if first phase is Document testing – individual usage testing of document testing – as well as testing of entire document management feature – will not go back to documents to retest when a new feature is being rolled out – test cases – who will prepare them? – prepared as a team – e-Builder to NJDOT – test scripts will be provided to NJDOT
Trainers will be Austin and Bryon – Training is not outsourced – done by BAs – three different types of training – team approach for Admin Training – NJDOT will be able to write their own forms – workflows – etc. – not just maintain current system – it’s the entire system – enhancing e-Builder for future
Users – NJDOT users and external users –
Training Guides
User Guides
All training – except for online refreshers – will be done onsite – electronic PDF copies – expectation for NJDOT – is a training location – and sitting in front of a computer – users will need to bring in real NJDOT data –
Adoption
Adopt what was laid out in adoption document
Question on the Floor – electronic invoicing – who will be delivering the training to NJDOT users – someone said that it is close to being done today – electronic invoicing
Will address any feedback that comes out of adoption period – combo of remote sessions and onsite support
Out of Adoption – will be phase transitions – phase transitions will overlap
Will have a final transition to Account Management staff – this will be the PoC for rest of e-Builder time

11. Design Kickoff Discovery Design Configure Test Train Adoption
Objectives
Define and finalize Design Requirements
Define and finalize the structured workflows
Define and finalize the integration process
Define the Adoption Path
Required Resources
PSU Core Team
PSU SME’s
Deliverables
Solution Document
Process Document
Adoption Plan
Integration Requirements
Custom Development Requirements
Onsite Sessions
Multiple onsite sessions
Scheduled to accommodate SME’s
Onsite sessions are Tuesday - Thursday
Reviewed Implementation Phases
Currently in Kick-off
Will move to Discovery Phase – Objectives – fundamental understanding of e-Builder – what does NJDOT want e-Builder to do – understand what e-Builder will do at the 30K level – second objective – why does NJDOT do business the way they do – how/why/requirements – lot of Q&A – sample documents – diagrams – workflows – fundamental to this process is core team
When will start using e-Builder? – implementation in e-Builder – NJDOT will be active e-Builder users – Core Team – s will be minimal – will have an implementation dashboard – all documents will be in an e-Builder document structure – receive value from e-Builder today
Mix of onsite and remote sessions – where most effective
Meeting Minutes taken in e-Builder and issued through e-Builder
Build what we understand
Design
Done on site
Give NJDOT an idea of what e-Builder will be building
Documentation and prototyping
White boarding
Discussion
Process Requirements
Solution Document
Deliverables
Adoption Plan – how ever many phases equals how many adoption plans – how will we test this? – Sign off on adoption plan – NJDOT will be held accountable to Adoption Plan deliverables – in time frame allotted for Adoption Plan
Custom Development Requirements
Integration Requirements
Design Session – 3 days – agenda will be delivered to NJDOT – hourly based – allows for SMEs to come into Design Meetings – 2 week notice to plan and schedule Design topics – 8 hours a day for T, W, and Th – no questions
Configuration
Breather for NJDOT
Will have BETA2 site as well
e-Builder is now building items that came out of Design session
Account Config
Internal Testing
Testing
UAT – take NJDOT data and NJDOT users and drive system – use script – will model a normal transaction – need to provide real-world NJDOT data
Client Acceptance Letter – Scope met – item complete – ready to train and roll-out
UAT will be done onsite – not a full team involvement – e-Builder will not do the driving – NJDOT users will be entering data
Testing – Unit testing or System Wide testing – Unit inside of phase testing – if first phase is Document testing – individual usage testing of document testing – as well as testing of entire document management feature – will not go back to documents to retest when a new feature is being rolled out – test cases – who will prepare them? – prepared as a team – e-Builder to NJDOT – test scripts will be provided to NJDOT
Trainers will be Austin and Bryon – Training is not outsourced – done by BAs – three different types of training – team approach for Admin Training – NJDOT will be able to write their own forms – workflows – etc. – not just maintain current system – it’s the entire system – enhancing e-Builder for future
Users – NJDOT users and external users –
Training Guides
User Guides
All training – except for online refreshers – will be done onsite – electronic PDF copies – expectation for NJDOT – is a training location – and sitting in front of a computer – users will need to bring in real NJDOT data –
Adoption
Adopt what was laid out in adoption document
Question on the Floor – electronic invoicing – who will be delivering the training to NJDOT users – someone said that it is close to being done today – electronic invoicing
Will address any feedback that comes out of adoption period – combo of remote sessions and onsite support
Out of Adoption – will be phase transitions – phase transitions will overlap
Will have a final transition to Account Management staff – this will be the PoC for rest of e-Builder time

12. Configuration Objectives Required Resources Deliverables
Kickoff
Discovery
Design
Configure
Test
Train
Adoption
Objectives
Configure Production account
Configure BETA account where necessary
Account Testing
Configure Processes
Process Testing
Required Resources
Limited
Deliverables
Configured Account
Custom Development
QA/Internal Testing
Configuration Calls
If required, configuration calls to clarify any questions from the e-Builder Enterprise team to the PSU Core Team
Reviewed Implementation Phases
Currently in Kick-off
Will move to Discovery Phase – Objectives – fundamental understanding of e-Builder – what does NJDOT want e-Builder to do – understand what e-Builder will do at the 30K level – second objective – why does NJDOT do business the way they do – how/why/requirements – lot of Q&A – sample documents – diagrams – workflows – fundamental to this process is core team
When will start using e-Builder? – implementation in e-Builder – NJDOT will be active e-Builder users – Core Team – s will be minimal – will have an implementation dashboard – all documents will be in an e-Builder document structure – receive value from e-Builder today
Mix of onsite and remote sessions – where most effective
Meeting Minutes taken in e-Builder and issued through e-Builder
Build what we understand
Design
Done on site
Give NJDOT an idea of what e-Builder will be building
Documentation and prototyping
White boarding
Discussion
Process Requirements
Solution Document
Deliverables
Adoption Plan – how ever many phases equals how many adoption plans – how will we test this? – Sign off on adoption plan – NJDOT will be held accountable to Adoption Plan deliverables – in time frame allotted for Adoption Plan
Custom Development Requirements
Integration Requirements
Design Session – 3 days – agenda will be delivered to NJDOT – hourly based – allows for SMEs to come into Design Meetings – 2 week notice to plan and schedule Design topics – 8 hours a day for T, W, and Th – no questions
Configuration
Breather for NJDOT
Will have BETA2 site as well
e-Builder is now building items that came out of Design session
Account Config
Internal Testing
Testing
UAT – take NJDOT data and NJDOT users and drive system – use script – will model a normal transaction – need to provide real-world NJDOT data
Client Acceptance Letter – Scope met – item complete – ready to train and roll-out
UAT will be done onsite – not a full team involvement – e-Builder will not do the driving – NJDOT users will be entering data
Testing – Unit testing or System Wide testing – Unit inside of phase testing – if first phase is Document testing – individual usage testing of document testing – as well as testing of entire document management feature – will not go back to documents to retest when a new feature is being rolled out – test cases – who will prepare them? – prepared as a team – e-Builder to NJDOT – test scripts will be provided to NJDOT
Trainers will be Austin and Bryon – Training is not outsourced – done by BAs – three different types of training – team approach for Admin Training – NJDOT will be able to write their own forms – workflows – etc. – not just maintain current system – it’s the entire system – enhancing e-Builder for future
Users – NJDOT users and external users –
Training Guides
User Guides
All training – except for online refreshers – will be done onsite – electronic PDF copies – expectation for NJDOT – is a training location – and sitting in front of a computer – users will need to bring in real NJDOT data –
Adoption
Adopt what was laid out in adoption document
Question on the Floor – electronic invoicing – who will be delivering the training to NJDOT users – someone said that it is close to being done today – electronic invoicing
Will address any feedback that comes out of adoption period – combo of remote sessions and onsite support
Out of Adoption – will be phase transitions – phase transitions will overlap
Will have a final transition to Account Management staff – this will be the PoC for rest of e-Builder time

13. Testing Kickoff Discovery Design Configure Test Train Adoption
Objectives
Validation of account configuration
Validation of process configuration
Validation of Custom development
Validation of Integrations
Required Resources
PSU Core Team
PSU SME’s
Deliverables
Approved Test Scripts
Client Acceptance Letter
Testing Session
Sessions to execute, validate and approve UAT plan
Reviewed Implementation Phases
Currently in Kick-off
Will move to Discovery Phase – Objectives – fundamental understanding of e-Builder – what does NJDOT want e-Builder to do – understand what e-Builder will do at the 30K level – second objective – why does NJDOT do business the way they do – how/why/requirements – lot of Q&A – sample documents – diagrams – workflows – fundamental to this process is core team
When will start using e-Builder? – implementation in e-Builder – NJDOT will be active e-Builder users – Core Team – s will be minimal – will have an implementation dashboard – all documents will be in an e-Builder document structure – receive value from e-Builder today
Mix of onsite and remote sessions – where most effective
Meeting Minutes taken in e-Builder and issued through e-Builder
Build what we understand
Design
Done on site
Give NJDOT an idea of what e-Builder will be building
Documentation and prototyping
White boarding
Discussion
Process Requirements
Solution Document
Deliverables
Adoption Plan – how ever many phases equals how many adoption plans – how will we test this? – Sign off on adoption plan – NJDOT will be held accountable to Adoption Plan deliverables – in time frame allotted for Adoption Plan
Custom Development Requirements
Integration Requirements
Design Session – 3 days – agenda will be delivered to NJDOT – hourly based – allows for SMEs to come into Design Meetings – 2 week notice to plan and schedule Design topics – 8 hours a day for T, W, and Th – no questions
Configuration
Breather for NJDOT
Will have BETA2 site as well
e-Builder is now building items that came out of Design session
Account Config
Internal Testing
Testing
UAT – take NJDOT data and NJDOT users and drive system – use script – will model a normal transaction – need to provide real-world NJDOT data
Client Acceptance Letter – Scope met – item complete – ready to train and roll-out
UAT will be done onsite – not a full team involvement – e-Builder will not do the driving – NJDOT users will be entering data
Testing – Unit testing or System Wide testing – Unit inside of phase testing – if first phase is Document testing – individual usage testing of document testing – as well as testing of entire document management feature – will not go back to documents to retest when a new feature is being rolled out – test cases – who will prepare them? – prepared as a team – e-Builder to NJDOT – test scripts will be provided to NJDOT
Trainers will be Austin and Bryon – Training is not outsourced – done by BAs – three different types of training – team approach for Admin Training – NJDOT will be able to write their own forms – workflows – etc. – not just maintain current system – it’s the entire system – enhancing e-Builder for future
Users – NJDOT users and external users –
Training Guides
User Guides
All training – except for online refreshers – will be done onsite – electronic PDF copies – expectation for NJDOT – is a training location – and sitting in front of a computer – users will need to bring in real NJDOT data –
Adoption
Adopt what was laid out in adoption document
Question on the Floor – electronic invoicing – who will be delivering the training to NJDOT users – someone said that it is close to being done today – electronic invoicing
Will address any feedback that comes out of adoption period – combo of remote sessions and onsite support
Out of Adoption – will be phase transitions – phase transitions will overlap
Will have a final transition to Account Management staff – this will be the PoC for rest of e-Builder time

14. Training Kickoff Discovery Design Configure Test Train Adoption
Objectives
Provide in class training
Provide resources for self paced learning
Required Resources
Account Administrators
Internal Users
External Users
Deliverables
Admin Training Guides
User Training Guides
Practice Projects
Completed Training sessions
Onsite Session
Administrator Training
Train-the-Trainer
User Training
Role-based approach for internal and external users
Reviewed Implementation Phases
Currently in Kick-off
Will move to Discovery Phase – Objectives – fundamental understanding of e-Builder – what does NJDOT want e-Builder to do – understand what e-Builder will do at the 30K level – second objective – why does NJDOT do business the way they do – how/why/requirements – lot of Q&A – sample documents – diagrams – workflows – fundamental to this process is core team
When will start using e-Builder? – implementation in e-Builder – NJDOT will be active e-Builder users – Core Team – s will be minimal – will have an implementation dashboard – all documents will be in an e-Builder document structure – receive value from e-Builder today
Mix of onsite and remote sessions – where most effective
Meeting Minutes taken in e-Builder and issued through e-Builder
Build what we understand
Design
Done on site
Give NJDOT an idea of what e-Builder will be building
Documentation and prototyping
White boarding
Discussion
Process Requirements
Solution Document
Deliverables
Adoption Plan – how ever many phases equals how many adoption plans – how will we test this? – Sign off on adoption plan – NJDOT will be held accountable to Adoption Plan deliverables – in time frame allotted for Adoption Plan
Custom Development Requirements
Integration Requirements
Design Session – 3 days – agenda will be delivered to NJDOT – hourly based – allows for SMEs to come into Design Meetings – 2 week notice to plan and schedule Design topics – 8 hours a day for T, W, and Th – no questions
Configuration
Breather for NJDOT
Will have BETA2 site as well
e-Builder is now building items that came out of Design session
Account Config
Internal Testing
Testing
UAT – take NJDOT data and NJDOT users and drive system – use script – will model a normal transaction – need to provide real-world NJDOT data
Client Acceptance Letter – Scope met – item complete – ready to train and roll-out
UAT will be done onsite – not a full team involvement – e-Builder will not do the driving – NJDOT users will be entering data
Testing – Unit testing or System Wide testing – Unit inside of phase testing – if first phase is Document testing – individual usage testing of document testing – as well as testing of entire document management feature – will not go back to documents to retest when a new feature is being rolled out – test cases – who will prepare them? – prepared as a team – e-Builder to NJDOT – test scripts will be provided to NJDOT
Trainers will be Austin and Bryon – Training is not outsourced – done by BAs – three different types of training – team approach for Admin Training – NJDOT will be able to write their own forms – workflows – etc. – not just maintain current system – it’s the entire system – enhancing e-Builder for future
Users – NJDOT users and external users –
Training Guides
User Guides
All training – except for online refreshers – will be done onsite – electronic PDF copies – expectation for NJDOT – is a training location – and sitting in front of a computer – users will need to bring in real NJDOT data –
Adoption
Adopt what was laid out in adoption document
Question on the Floor – electronic invoicing – who will be delivering the training to NJDOT users – someone said that it is close to being done today – electronic invoicing
Will address any feedback that comes out of adoption period – combo of remote sessions and onsite support
Out of Adoption – will be phase transitions – phase transitions will overlap
Will have a final transition to Account Management staff – this will be the PoC for rest of e-Builder time

15. Adoption Kickoff Discovery Design Configure Test Train Adoption
Objectives
Monitor current state
Ensure success criteria is being accomplished
Ensure value is being achieved
Required Resources
Account Administrators
Internal Users
External Users
Deliverables
Adoption Plan
Adoption Calls
(3) Schedule Adoption checkpoint calls through this phase
Reviewed Implementation Phases
Currently in Kick-off
Will move to Discovery Phase – Objectives – fundamental understanding of e-Builder – what does NJDOT want e-Builder to do – understand what e-Builder will do at the 30K level – second objective – why does NJDOT do business the way they do – how/why/requirements – lot of Q&A – sample documents – diagrams – workflows – fundamental to this process is core team
When will start using e-Builder? – implementation in e-Builder – NJDOT will be active e-Builder users – Core Team – s will be minimal – will have an implementation dashboard – all documents will be in an e-Builder document structure – receive value from e-Builder today
Mix of onsite and remote sessions – where most effective
Meeting Minutes taken in e-Builder and issued through e-Builder
Build what we understand
Design
Done on site
Give NJDOT an idea of what e-Builder will be building
Documentation and prototyping
White boarding
Discussion
Process Requirements
Solution Document
Deliverables
Adoption Plan – how ever many phases equals how many adoption plans – how will we test this? – Sign off on adoption plan – NJDOT will be held accountable to Adoption Plan deliverables – in time frame allotted for Adoption Plan
Custom Development Requirements
Integration Requirements
Design Session – 3 days – agenda will be delivered to NJDOT – hourly based – allows for SMEs to come into Design Meetings – 2 week notice to plan and schedule Design topics – 8 hours a day for T, W, and Th – no questions
Configuration
Breather for NJDOT
Will have BETA2 site as well
e-Builder is now building items that came out of Design session
Account Config
Internal Testing
Testing
UAT – take NJDOT data and NJDOT users and drive system – use script – will model a normal transaction – need to provide real-world NJDOT data
Client Acceptance Letter – Scope met – item complete – ready to train and roll-out
UAT will be done onsite – not a full team involvement – e-Builder will not do the driving – NJDOT users will be entering data
Testing – Unit testing or System Wide testing – Unit inside of phase testing – if first phase is Document testing – individual usage testing of document testing – as well as testing of entire document management feature – will not go back to documents to retest when a new feature is being rolled out – test cases – who will prepare them? – prepared as a team – e-Builder to NJDOT – test scripts will be provided to NJDOT
Trainers will be Austin and Bryon – Training is not outsourced – done by BAs – three different types of training – team approach for Admin Training – NJDOT will be able to write their own forms – workflows – etc. – not just maintain current system – it’s the entire system – enhancing e-Builder for future
Users – NJDOT users and external users –
Training Guides
User Guides
All training – except for online refreshers – will be done onsite – electronic PDF copies – expectation for NJDOT – is a training location – and sitting in front of a computer – users will need to bring in real NJDOT data –
Adoption
Adopt what was laid out in adoption document
Question on the Floor – electronic invoicing – who will be delivering the training to NJDOT users – someone said that it is close to being done today – electronic invoicing
Will address any feedback that comes out of adoption period – combo of remote sessions and onsite support
Out of Adoption – will be phase transitions – phase transitions will overlap
Will have a final transition to Account Management staff – this will be the PoC for rest of e-Builder time

16. Project Communication
Monthly schedule updates
Detailed schedule update
Update of e-Builder Implementation Dashboard.
Bi-Weekly core team status calls
Champion & stakeholders
Risk Assessment and Mitigation
Scope Adjustments and Change Management
e-Builder implementation project
House all reference documents
House all project deliverables
Route Action Items and Risk Items
Store Meeting Minutes
Implementation Dashboard
Schedule
Updated monthly – milestone based – key components – decision making on NJDOT items – this is critical for NJDOT
This will be on e-Builder implementation dashboard
Bi-Weekly core team status calls
Start off
This is *in addition* to all other calls
Focus – is around risk assessment and mitigation – Scope Budget Schedule – Scope adjustments – review as needed – Champion, Core Team, and Stakeholders
e-Builder Implementation Project – passwords and logins will be received tomorrow night – for NJDOT – only Core Team will have access – add SMEs too?

17. Common Project Risk(s)
Executive Sponsorship
Demand 1st value
Stay engaged
Set the tone at meetings
Enterprise Communication
Early and often
Resource Availability
The right people
The right amount of time
Feature Over Function
Focus on solutions
Project Fatigue
Focus on 1st value
Phased rollouts
Project Fatigue
12 to 14 months
Quickly identify 1st value – get buy-in
Phased roll-outs
Pilot Projects
Feature over Function
Focus on solutions
Deliver solution that hits 85% mark
Looking at all e-Builder can do instead of what will provide NJDOT value right now
Executive Sponsorship
People in place to make decisions
Contractor Signers example
Question on the floor – take the place of the AD12? – wish department actions go through e-Builder – this is not in the current scope – help champion some of these process earlier rather than later
Question on the floor – how can we best prepare for what we need to deliver 12 to 14 months later? – Management must be at the ground level –
Question on the floor – Local Aid PM system – how will the scope for Local Aid be addressed? – Local Aid will be in part of some of the design sessions
Have necessary people in the meeting to make the decision
Enterprise Communication
Often
Multiple points of communication
Communication out to departments and to end-users
End-users need to hear the message as soon as possible – so that they are not surprised at training
Resource Availability
Key priority
Can and will have to make decisions with Core Team in the room
When onsite – please be available – make resources available – put proxy in place that has the same decision making as you do

18. 3. Scripted Demonstrations
3.1 Projects and Sub-Projects
3.2 Data Management and Turnover
3.3 Bidding
3.4 Mobile Access
3.5 Schedule Management

19. 3.1 Project and Sub-Projects

20. 3.2 Data Management and Turnover

21. Submittal Process Example

22. 3. Turnover Example

23. 3.3 Bidding

24. Bidding

25. 3.4 Mobile Access

26. 3.5 Schedule Management

27. 4. Unscripted Demonstrations
4.1 Bluebeam
4.2 Workflow Designer

28. 4.1 Bluebeam

29. 4.2 Workflow Designer

30. Questions?
We value your feedback